THE CANONICAL DISTRIBUTION OF OPENSTACK
The starting point our lab is the following:
This article will demonstrate how to launch the first Openstack instance. In order to launch the Openstack instance we need to create a new network security group, rule & a key pairs we’ll use to access to instance from our network. On this new rule we will add the SSH and the Ping protocol. Note that once we have download the key pair , there is no way to download it again due to security reason.
1 STEP – CREATE AN IMAGE ON OPENSTACK
It’s time to create an new image of using to our instance, this task is done using one of the following image:
- CentOS 7 – http://cloud.centos.org/centos/7/images/
- CentOS 6 – http://cloud.centos.org/centos/6/images/
- Fedora 23 – https://download.fedoraproject.org/pub/fedora/linux/releases/23/Cloud/
- Ubuntu – http://cloud-images.ubuntu.com/
- Debian – http://cdimage.debian.org/cdimage/openstack/current/
- Windows Server 2012 R2 – https://cloudbase.it/windows-cloud-images/#download
for our lab we’ve used
the file is that:
Once we’ve download that, we can proceed with the following task, remember that we’re using the bundle of Openstack LXD:
2 STEP – CREATE A SECURITY GROUP
After that we need to make the login with our user firstname.lastname@example.org
its own network after we’ve configured that via admin user, will be that
Now goto back to Juju gui and apply this modification on Neutron-Api. Ensure that within neutron-api charm, “neutron-security-groups” is set to True, ash shown here:
save and deploy the new configuration, now we can proceed with the rest. Navigate to Project ->Compute -> Access & Security on Openstack and create new one:
Once the group has been created successfully, Click on “Manage Rules” .
now adding a rule to permit ssh & ping from anywhere to the instances. The new Group Security Rules will be that:
3 STEP – CREATE U1604PRO ROUTE
For our email@example.com user the network topology at the moment is the following
now navigate Project -> Network -> Routers on Openstack. We’ll call it “router”
add its new interface,
The sixth part is done see you to next one.
Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.
“We learn from our mistakes”