City Cloud OpenStack was launched to the public just 10 days ago and we are off to a great start. Among all the features that we offer, and will offer in the near future, we will now focus on 2 specific features that will appeal to both technical and operational managers.
Users and projects
By taking advantage of the projects and users feature in City Cloud OpenStack you can get better control over access, cost and just plain overview of your server infrastructure. Here are some quick tips on how to use these features and some thoughts on when it can come in handy.
Adding a project
Click Settings -> Manage Projects -> Create Project. Give your project a name and a description and hit Create Project.
Each project has it’s own quota which you can see by clicking the little wheel beside the project name. The quota is set by the system at this point but we are constantly building on these features and you will soon be able to set your own quotas for number of cores, storage and other parameters of an individual project.
So, how is this useful? At this stage, the project feature is merely a way to stay organized. Each project in City Cloud OpenStack is like working with a blank canvas in terms of what resources are present and presented to you when working in the particular project. IP-adresses in the pool, volumes and snapshots in one project is not visible for another project and vice versa. Knowing the cost (and soon setting spending caps and other limitations) of a certain project is also a huge benefit for operational managers in particular.
Managing users and access to features and projects
When we combine the Projects feature with the Users feature we can start creating a hierarchy and control access for all users in our account. This is where access and security comes in to play.
Click the Account button in your top right corner and then the Users tab -> Click Add user -> Enter the username and password for the new user.
Now it’s time to delegate access to your users and this is where that project we created earlier can come in handy. As you can see, when assigning privileges for Servers/OpenStack, you are presented with an option to give that user Project Access.
This feature could be used when you have different teams working on different projects and don’t want them to mix. Sometimes, giving everyone access to all parts of your infrastructure might not be the best option.
Besides controlling access to individual projects, the administrator can delegate access to all parts of City Cloud. A person from the finance department for instance, does he/she need access to anything other than the invoices? Or that trainee that you just hired, should he/she really be able to allocate new resources and make changes to existing projects or just stay in read only mode?
A number of people might need access to your City Cloud account and there is nothing wrong with that. Just take a second to think about who needs access to what and set privileges and projects accordingly.