Main Page: Difference between revisions
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
You can make [[Resource query examples|queries]] for nova resources; currently Nova instances have semantic properties enabled. |
You can make [[Resource query examples|queries]] for nova resources; currently Nova instances have semantic properties enabled. |
||
After logging in, you can also access [https://gerrit.wikimedia.org Gerrit]; if you wish to do git checkouts of the puppet repositories, you'll need to log into [https://gerrit.wikimedia.org Gerrit], and add your SSH key there as well. Note: it would be nice if Gerrit could use LDAP for its SSH keystore, instead of its database; I've opened a [http://code.google.com/p/gerrit/issues/detail?id=1124 bug for this], if you'd like to help, please add that feature to Gerrit! |
|||
=== Admins === |
=== Admins === |
||
Line 53: | Line 55: | ||
* '''Q:''' I was added to a group that gives me access to something in git, but it isn't working, what's wrong? |
* '''Q:''' I was added to a group that gives me access to something in git, but it isn't working, what's wrong? |
||
** '''A:''' Once you have been added to the group, you need to log out of gerrit, then back in. Gerrit pulls its groups from LDAP, but caches them. Logging out, then back in re-synchronizes your groups, and thus clears the cache. |
** '''A:''' Once you have been added to the group, you need to log out of gerrit, then back in. Gerrit pulls its groups from LDAP, but caches them. Logging out, then back in re-synchronizes your groups, and thus clears the cache. |
||
== Git/Gerrit and the puppet repositories == |
|||
Note: Access is currently limited to staff developers and operations engineers. This will change soon. |
|||
=== Checking out the branches === |
|||
__NOTOC__ |
__NOTOC__ |
Revision as of 18:24, 9 September 2011
Access rights
Anonymous users
You'll need to create an account.
Logged in users
After creating an account, you can:
Once you add a key, you'll be able to log into an instance in the main project testlabs. It may take up to 30 minutes for your key to be propagated to all instances.
If you'd like to create instances, you'll need to have an admin add you to a project, and to the sysadmin role in that project.
You can make queries for nova resources; currently Nova instances have semantic properties enabled.
After logging in, you can also access Gerrit; if you wish to do git checkouts of the puppet repositories, you'll need to log into Gerrit, and add your SSH key there as well. Note: it would be nice if Gerrit could use LDAP for its SSH keystore, instead of its database; I've opened a bug for this, if you'd like to help, please add that feature to Gerrit!
Admins
Wiki Admin
If you are a wiki admin, you can:
- Create/delete Nova projects and manage project and project role membership
- Manage global role membership.
- Manage sudo policies.
Net Admins
If you are a NetAdmin, you can:
- Allocate and associate public IP addresses, and add public DNS entries to instances
- Manage security groups and rules.
Sys Admins
If you are a sysadmin, you can:
After creating an instance, you'll get an email notifying you that it is ready to be logged into. If you did not add an SSH key prior to creating the instance, you'll need to wait until your key is propagated to the instances (which can take an additional 30 minutes).
Cloud Admins
In addition to all actions that sysadmins and netadmins, you can:
Access FAQ
- Q: I was added to a group that gives me access to something in git, but it isn't working, what's wrong?
- A: Once you have been added to the group, you need to log out of gerrit, then back in. Gerrit pulls its groups from LDAP, but caches them. Logging out, then back in re-synchronizes your groups, and thus clears the cache.
Git/Gerrit and the puppet repositories
Note: Access is currently limited to staff developers and operations engineers. This will change soon.