KEMBAR78
Open Stack | PDF
0% found this document useful (0 votes)
36 views16 pages

Open Stack

OpenStack administrators manage projects, users, and roles to organize cloud resources, where projects own virtual machines and users perform tasks based on assigned roles. Key constructs in OpenStack Compute include images, flavors, volumes, networks, and instances, which define the capabilities and resources of virtual machines. Users can be created and assigned to projects with specific roles, while networks can be managed and configured for connectivity within the cloud environment.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
36 views16 pages

Open Stack

OpenStack administrators manage projects, users, and roles to organize cloud resources, where projects own virtual machines and users perform tasks based on assigned roles. Key constructs in OpenStack Compute include images, flavors, volumes, networks, and instances, which define the capabilities and resources of virtual machines. Users can be created and assigned to projects with specific roles, while networks can be managed and configured for connectivity within the cloud environment.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 16
Projects, Users, and Roles ‘© An Openstack administrator creates and manages three primary constructs: ‘© Project: An organization unit in the cloud to which users are assigned: for example, In OpenStack Compute a project ‘owns virtual machines (VMs) Users: Assigned to a project: perform tasks based on the roles defined + Roles: Actions auser can perform: assigned toa user-project pair Images, Flavors, Volume, Network, and Instances In OpensStack Compute, the important constructs are: Images 12 The VM image; multiple formats are supported Flavors 18 The compute, memory, and storage capacity of compute instances Volume 18 Detachable block storage device, attached to one compute instance Network © Avirtual network attached to one or more instances Instances 8 AVMcreated in OpenStack compute Projects ‘©. Organizational units in OpenStack to which users are assigned: © Owns resources such as VMs in Compute + Access trom Identity > Projects hace = notes os Creating a Project Define a project name, project members, and optionally project groups: Create Projet yen ty Users (© Users are accounts that are members of one or more projects; roles define actions that users can perform Access from Identity > Users Creating a User Define username, e-mail, password, project, and role to be assigned to the user. Roles (© Define the actions users can perform Access from the Identity > Roles workspace = Roles Images © Create or manage virtual machines rm Project > Compute > Images: (© Create globally available images from Admin > Compute > Images Creating an Image Define the image name, browse for the Image fle, define image requirements and metadata, Flavors ©. Define the compute, memory, and storage capacity of Nova computing instances Creating a Flavor Define vCPUs, RAM, Disk Space, and the project in which the flavor can be used! Virtual Networks (Openstack implements virtual networks by defining multiple networks for tenant VMs + Networks are ereated within projects for connectivity + Project networks ae fully isolated + Network isolation and overlay technologies supported are: ‘8 Flat—Allinstances onthe same network, no VLAN tagging or network segregation 8 VLAN-Project networks are created using VLAN IDs mapping into VLANs present fon the physical network © Generic routing encapsulation (GRE) and Virtual Extensible LAN (VXLAN)— Encapsulation protocols to create overlay networks; anetworking router is. required to enable traffic low outside a project network # Provider networks offer Layer 2(L2) connectivity + Routed provider networks offer Layer 3 (L3) connectivity to instances and map to existing L3 networks in the data center Virtual Networks ©. Self-service networks Virtual networks created within OpenStack that use virtual routers to interact with provider and external networks ‘© Mostly use overlay protocols such as VLAN or GRE. The communication with provider networks happens through source Network Address Translation (NAT) or virtual routers Hl @ Newton Router (Compute Noce Managing a Network CCreate a Network from Project » Network > Networks: Creating a Network Define network name, subnet, and subnet details: eae Network

You might also like