Activity: Cost analysis

Estimate the costs for the scenario using Simple Monthly Calculator to estimate the costs for the scenario.

Saved caluculation BOM Link,

Amazon EC2 service – Which denotes the virtual machines in the cloud space with OS level control which is available based on your requirement. cost for this service preliminary depends on what virtual hardware profile/instance to be chosen such as vCPU, Virtual memory etc….

Amazon S3 service – Which denotes storage service of AWS. This storage can be used to store objects such as files, folders. however this storage space cannot be used to install software. required storage capacity and it’s read / write frequency /data scaninig and disaster recoevery between region were key indicaters when it comes to select Amazon S3 servvice in this BOM.

Amazon S3 route service – This is the DNS service with high availablity in Amazon AWS. cost for this service is depends on no of zones, DNS recursive queries (per month) etc…

Amazon RDS Service – which is the platform to execute relational databases such as MySQL, MariaDB, PostgreSQL, Oracle SQL servers. Cost for this service is depends on database storage capacity and instance ( no of input and output )

Amazon ELB- Elastic Load Balancing automatically distributes incoming application traffic across multiple targets. basically cost of this service is depends on the measures the dimensions on which the Application Load Balance processes your traffic. 

AWS Support – This is the service level agreement (SLA) between AWS cloud provider and the customer. AWS Support provides a mix of tools and technology, people, and programs designed to proactively help customer.

Configure Network & Routing in OpenStack

In this lab we will configure two networks and create a router to allow communication between the networks

01. Create Networks

Create a network named “GREEN”

Assign 192.168.0.0/24 subnet to GREEN network. First IP address will be reserved as default gateway since Gateway IP address is not defined.

Enable DHCP service for this subnet. In that way instance will be able to get IP address automatically from this subnet if this subnet is assigned to the instance.
Created a BLUE network and BLUE_SN subnet with the address 192.168.1.0/24 as well

02. Create Instance

Launch 2 instances with the name GREEN_1 and GREEN_2 respectively.

Count value of this will be denoted as number of instances

Cirros vm instance allocated

Selected predefined m1.nano compute resource

Allocated GREEN_SN subnet for this instance

This shows GREEN-1 and GREEN-2 instance are taken DHCP IP addresses from the GREEN_SN subnet pool.

Additionally created a instance called BLUE with assigning BLUE_SN subnet . According to the above figure BLUE instance has received 192.168.1.80 ip address from BLUE network DHCP scope from the DHCP server.

GREEN-1 instance is up and running

GREEN-2 instance is up and running
BLUE instance is up and running

GREEN-1 (192.168.0.83) instance able to ping GREEN-2 (192.168.0.249) as both the instances are belongs to same subnet but cannot ping BLUE (192.168.1.80) instance which belongs to different subnet.

03. Review the OpenStack network topology graph

Topology show no IP link between GREEN and BLUE network domain. there must be routing device to be placed in order to communicate between above network domains.

04. Create a router to route packets between the networks

Created router named ROUTER_1

Added both GREEN_SN and BLUE_SN subnet to the ROUTER_1. First IP address of each subnet will be allocated to the respective router interface

Topology show IP router (ROUTER_1) has been placed to communicate between GREEN-1/GREEN-2 and BLUE instances

GREEN-1 instance (192.168.0.83) able to ping BLUE instance (192.168.1.80) after placing ROUTER_1 having both networks connected to it.

05. Investigating an OpenStack networking feature of your choice

I would like to explore little description about Flat Network in Openstack. Flat networks were the network type provided with the original nova networking. With flat networks all projects connect to the same network and the outside world. It is hard to protect internal services that do not need to face the internet. Additionally, security is reduced as all
instances share the same network no matter the owner of the instance.

If you needed to enable Flat Networks edit the file:
/etc/neutron/plugins/ml2/ml2_conf.ini then add,

type_drivers = vxlan,flat

i tried to install opestack packstack ( Pack stack is openstack all in one repository) and installed in my PC on vmware workstation instance but ended up with errors. need more time to research however with other activities i did not have time to more on research regarding this implementation

Reference: https://wiki.openstack.org/wiki/Packstack#Summary

Install OpenStack Private Cloud

01. Installing Virtualbox

In this Lab, we are going to install Openstack free open standard cloud computing platform on Ununtu OS. for that, it is required to install virtual box computer emulation software on local windows PC.

Create a Host Only Network in VirtualBox to allow communication between the host and guest (Ubuntu OS). Also configure DHCP server over host adapter to serve automatic IP assignment to the guest OS.

Creating a VM named Openstack with 4096MB RAM and 30GB virtual hard disk space

Below command will enable nested hardware virtualization for the Openstack guest VM

“C:\Program Files\Oracle\VirtualBox\VBoxManage” modifyvm Openstack –nested-hw-virt on

NAT option is assigned to the Adapter1 in order to provide internet connectivity for the guest VM and Adapter2 select the Host-Only mode, in that way, Guest VM will be able to get the IP address via Virtualbox DHCP server.

Summery of Guest VM specification

02. Installing Ubuntu on Virtualbox

sudo -i
apt update -y && apt upgrade -y

03.Installing Openstack from DevStack scripts

sudo useradd -s /bin/bash -d /opt/stack -m stack
echo “stack ALL=(ALL) NOPASSWD: ALL” | sudo tee /etc/sudoers.d/stack
sudo su – stack

git clone https://opendev.org/openstack/devstack
cd devstack

Create a local.conf file with four passwords preset at the root of the devstack git repo.
as well as assigned host IP address manually which also the IP address assigned by virtualbox DHCP server to the guest VM.

username: admin / Password : secret