SelfPortal | One for all virtualization abstraction layer | Infrastructure Automation library

by Altoros PHP Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | SelfPortal Summary

SelfPortal is a PHP library typically used in Devops, Infrastructure Automation applications. SelfPortal has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

SelfPortal is a service, that was created by an Altoros DevOps team in order to resolve problem with granting access to company resources for developers. It has started as a small, almost static web page, that helped developers to publish their websites into the global network, but over time became a utility, that provide wide possibilites to create virtual development environment, manage it and clear while necessary. Secure control over all the resources is a kind of main idea of our project.

Support

Quality

Security

License

Reuse

Support

SelfPortal has a low active ecosystem.

It has 22 star(s) with 7 fork(s). There are 14 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 6 have been closed. On average issues are closed in 68 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of SelfPortal is current.

Quality

SelfPortal has no bugs reported.

Security

SelfPortal has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

SelfPortal is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

SelfPortal releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed SelfPortal and discovered the below as its top functions. This is intended to give you an instant insight into SelfPortal implemented functionality, and help decide if they suit your requirements.

Create the mail body
Authenticate to the server
Attach all attachments
Connect to the SMTP server
Send data to the server
Connect to the POP3 server
type 2 . 3
Render the event
Authorise the POP3 server
Step 2 .

Get all kandi verified functions for this library.

SelfPortal Key Features

No Key Features are available at this moment for SelfPortal.

SelfPortal Examples and Code Snippets

No Code Snippets are available at this moment for SelfPortal.

Community Discussions

Trending Discussions on Infrastructure Automation

Create CloudFormation Yaml from existing RDS DB instance (Aurora PostgreSQL)

Azure DevOps CI with Web Apps for Containers

QUESTION

Create CloudFormation Yaml from existing RDS DB instance (Aurora PostgreSQL)

Asked 2020-Jun-05 at 00:59

I have an RDS DB instance (Aurora PostgreSQL) setup in my AWS account. This was created manually using AWS Console. I now want to create CloudFormation template Yaml for that DB, which I can use to create the DB later if needed. That will also help me replicate the DB in another environment. I would also use that as part of my Infrastructure automation.

...

ANSWER

Answered 2020-Jun-05 at 00:59

Unfortunately, there is no such functionality provided by AWS.

However, you mean hear about two options that people could wrongfully recommend.

CloudFormer

CloudFormer is a template creation beta tool that creates an AWS CloudFormation template from existing AWS resources in your account. You select any supported AWS resources that are running in your account, and CloudFormer creates a template in an Amazon S3 bucket.

Although it sounds good, the tool is no longer maintained and its not reliable (for years in beta).

Importing Existing Resources Into a Stack

Often people mistakenly think that this "generates yaml" for you from existing resources. The truth is that it does not generate template files for you. You have to write your own template which matches your resource exactly, before you can import any resource under control to CloudFormation stack.

Your only options is to manually write the template for the RDS and import it, or look for an external tools that could reverse-engineer yaml templates from existing resources.

Source https://stackoverflow.com/questions/62206364

QUESTION

Azure DevOps CI with Web Apps for Containers

Asked 2020-Mar-16 at 08:59

I'm struggling to set up a CI process for a web application in Azure. I'm used to deploying built code directly into Web Apps in Azure but decided to use docker this time.

In the build pipeline, I build the docker images and push them to an Azure Container Registry, tagged with the latest build number. In the release pipeline (which has DEV, TEST and PROD), I need to deploy those images to the Web Apps of each environment. There are 2 relevant tasks available in Azure releases: "Azure App Service deploy" and "Azure Web App for Containers". Neither of these allow the image source for the Web App to be set to Azure Conntainer Registry. Instead they take custom registry/repository names and set the image source in the Web App to Private Registry, which then requires login and password. I'm also deploying all Azure resources using ARM templates so I don't like the idea of configuring credentials when the 2 resources (the Registry and the Web App) are integrated already. Ideally, I would be able to set the Web App to use the repository and tag in Azure Container Registry that I specify in the release. I even tried to manually configure the Web Apps first with specific repositories and tags, and then tried to change the tags used by the Web Apps with the release (with the tasks I mentioned) but it didn't work. The tags stay the same.

Another option I considered was to configure all Web Apps to specific and permanent repositories and tags (e.g. "dev-latest") from the start (which doesn't fit well with ARM deployments since the containers need to exist in the Registry before the Web Apps can be configured so my infrastructure automation is incomplete), enable "Continuous Deployment" in the Web Apps and then tag the latest pushed repositories accordingly in the release so they would be picked up by Web Apps. I could not find a reasoble way to add tags to existing repositories in the Registry.

What is Azure best practice for CI with containerised web apps? How do people actually build their containers and then deploy them to each environment?

...

ANSWER

Answered 2020-Mar-16 at 08:59

Just set up a CI pipeline for building an image and pushing it to a container registry.

You could then use both Azure App Service deploy and Azure Web App for Containers task to handle the deploy.

The Azure WebApp Container task similar to other built-in Azure tasks, requires an Azure service connection as an input. The Azure service connection stores the credentials to connect from Azure Pipelines or Azure DevOps Server to Azure.

I'm also deploying all Azure resources using ARM templates so I don't like the idea of configuring credentials when the 2 resources (the Registry and the Web App)

You could also be able to Deploy Azure Web App for Containers with ARM and Azure DevOps.

How do people actually build their containers and then deploy them to each environment?

Kindly take a look at below blogs and official doc which may be helpful:

Source https://stackoverflow.com/questions/60693622

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install SelfPortal

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
Using vSphere and OpenStack in SelfPortal are optional. You can skip points 9 or 10 (or both) of this instruction respectively. Do not hesitate to use php -m to verify and check all php libraries installed. www-data ALL=NOPASSWD: /usr/sbin/nginx, /usr/bin/crontab, /bin/grep. 0 8 */1 * * /usr/bin/php /var/www/selfportal/modules/tasks.php --action notify. 1 0 */1 * * /usr/bin/php /var/www/selfportal/modules/tasks.php --action disable. 5 0 */1 * * /usr/bin/php /var/www/selfportal/modules/tasks.php --action delete. 10 0 */1 * * /usr/bin/php /var/www/selfportal/modules/tasks.php --action shutdown_vm. 15 0 */1 * * /usr/bin/php /var/www/selfportal/modules/tasks.php --action terminate_vm. Extract the archive you've downloaded from VMware website. Install SDK executng vmware-install.pl file.
Install NGINX, PHP (curl, json, ldap, mysqli, xml modules), MySQL/MariaDB, Perl (JSON, YAML, LWP::Protocol::https, Socket6, Switch, IO::Socket::SSL modules).
Create log folder, grant writing access to www-data and setup logrotate as well.
Clone this repo to /var/www/selfportal. Import database from /var/www/selfportal/db/portal.sql
Setup nginx to display selfportal at /var/www/selfportal. It's better to use https, you know it.
Rename /var/www/selfportal/config/config.php.example to /var/www/selfportal/config/config.php, change all values in accordance to your infrastruscture settings.
Copy config/sites-enabled/proxy.conf to /etc/nginx/sites-enabled/proxy.conf. Setup writing access for www-data.
Use sudo visudo command to add line to sudouers file:
Optional. If you want SelfPortal to terminate your VMs - please, add those lines to the root crontab:
Optional. Install Python OpenStack client. Go to https://pypi.python.org/pypi/python-openstackclient for details.
Optional. Install VMware vSphere Perl SDK (download it from vmware.com. Here is a link for vSphere 6.0 SDK).
While executing vmware-install.pl file you will be prompted to install required dependencies. When you will agree to do this - each dependency will be install for 1-2 minutes. But one of them, called Soap::Lite will be installed. Нажать Ctrl+C один раз.
Perl will throw warnings, until you change one line at /usr/share/perl/ /VMware/VICommon.pm, where is a version of your Perl. For 6.0 - it was a line #2332.
You can use install.sh file for semi-automatic install. Nevertheless, you'll still have to install Perl SDK (last point of instruction) manually.