In this guide we will previdet you with questions and answers that are usaully asked from our costumers:
Q: Is there IPV6 support in CityCloud openstack?
A: Currently not. Openstack does not yet support ipv6. It is in progress and will be supported later this year. ECP environment supports IPV6 so that can be used for now instead of openstack if customer must have ipv6 today.
For help with this contact our support by phone for more information. Request are sent to firstname.lastname@example.org
Q: My server is stuck in <whatever task-state it might be>. How can I fix it?
A: If a server is stuck in a specific task state (powering-on, powering-off, rebooting, etc.) it can be reset through our support.
Q: I've reached my quota limit. How can I increase quota?
A: You can increase quota by contacing our support.
Q: I don't want to use the service anymore. How can I shut it down?
A: You can do this in your controlpanel by removing everything on the account that costs money (disconnect all routers, remove all servers/volumes/floatingips/load balancer) in all projects. Ones that is done you can contact the support and they will verify that everything is erased and close down the service.
Q: My server no longer responds. I can't ssh/rdp or ping it
A: This requires some basic investigation. Check the following:
- 1. The IP the you try to connect to is connected to the server (you can see your IP in openstack controlpanel)
- 2. Check VNC console if server has crashed or has errors
- 3. Check that the security group that the server has applied allows the traffic that you are trying.
- 4. Check that server is connected to a network that has internet access. (When logged in, you can click on networks and it will display all networks and check if they have public connection, External connections)
- 5. If nothing else helps. Try rebooting the server / ask user to check settings in the servers operating system.
Q: How can I upload files to my swift container?
A: You need to use a swift client. Here are some instructions on how to use python_swift_client_instructions openstacks python swift client and cyberduck_swift_instructions cyberduck:
Cyberduck swift instructions cyberduck
Here is a short quickstart for howto setup cyberduck against citycloud swift project:
Works on windows and Mac.
Open connection -> choose swift (Openstack object storage)
Enter username and password (If you can't enter password click connect and it will ask you for password). When auth is completed you will receive a field to enter "Tenant". Tenant is the old name for "Project". Here you enter the ID of the project to work against. Currently we only allow one project per user in swift. (Due to V3-authentication not yet supported in swift clients)
You can find your tenant/project id in citycontrolpanel interface: api -> natiive openstack api -> click on swift tab and it will be listed.
Enter the ID in the tenant field in cyberduck.
Then you are all set to go. You have an upload link in the action button in cyberduck that you can use to upload your first files/folders.
Python swift client instructions openstacks python swift client
Några snabbexempel på hur man kan göra:
swift --os-username myuser --os-password mypassword --auth https://identity.se.storage.citycloud.com/v2.0/ --os-tenant-id myprojectid list
Om du i ovan rad byter ut "myuser", "mypassword" och "myprojectid" till att matcha den användare du har skapat så ska det fungera. Samtliga delar hittar/ställer du in på sidan i citycontrolpanel där du sköter swift api:et. (Just nu i det gränssnittet som ligger live så är det denna url: https://citycontrolpanel.com/openstack#openstack_api_access) Klicka på swift api tabben där så hittar du information om vilket projectID du har i swift samt att du kan skapa användare om du inte redan gjort det.
Som du ser i kommandoraden ovan så är det "list" som körs. VIlket då kommer lista vilka containers du har. Sen kan du köra list på en specifik container ("mycontainer" i detta exemplet):
swift --os-username myuser --os-password mypassword --auth https://identity.se.storage.citycloud.com/v2.0/ --os-tenant-id myprojectid list mycontainer
Lite fler exempel:
Ladda upp en fil eller folder till "mycontainer":
swift --os-username myuser --os-password mypassword --auth https://identity.se.storage.citycloud.com/v2.0/ --os-tenant-id myprojectid upload mycontainer < path>
Ladda hem en fil:
swift --os-username myuser --os-password mypassword --auth https://identity.se.storage.citycloud.com/v2.0/ --os-tenant-id myprojectid download mycontainer <filnamn>
Radera en fil:
swift --os-username myuser --os-password mypassword --auth https://identity.se.storage.citycloud.com/v2.0/ --os-tenant-id myprojectid delete mycontainer <filnamn>
Sen behöver man ju inte skicka det på command line utan du kan sätta det som environment variabel, du kan även begära en auth token och sen skicka med den i efterföljande requests, osv.
Om du är intresserad av swifts API, så kan du köra swift-klienten med "--debug", så kommer du se vilka headers och urls som används i varje request som du gör. Rätt smidigt sätt att se hur curl-anropen ser ut, få ut auth-keys, osv.
Q: How can I connect to Openstack API?
Openstack api instructions
Vi tillämpar Identity V3 för autentiseringen. Därmed är det enklast att autentisera sig med userId + lösen och inte username + lösen
Username är nämligen inte unikt över hela systemet i V3 utan olika users kan ha samma username.
Du ser userId på sidan där du styr API accesses i citycontrolpanel (api -> native openstack api)
Authdatan för att verifiera sig och skapa en token ser då ut ungefär så här när man encodar i json:
Openstack python client auth
Example on howto create auth token against openstack using python client:
$ openstack --os-auth-url "https://identity1.citycloud.com:5000/v3/
" --os-auth-type "v3password" --os-user-id "myUserId" --os-username "yourUsername" --os-password "yourPassword" --os-project-id "<yourProjectId>"
UserId + projectId can be found in native openstack api page in CCP.
Q: I created a server but I can't login
A: This could be due to several issues. Most common is that you tried to set a password that the operatingsystem does not allow ("Based on a dictionary word"). If the password is discarded, your user won't be created and instead the server is setup with the default user. ("centos", "ubuntu", "Administrator", "coreos", etc depending on operating system). If you created the server with an SSH-key, then you should be able to SSH to the server using the default username. For instance: "ssh centos@<serverIP>" and use the ssh-key and default user to access the server. If you did not provide an ssh-key and a discarded password then you have no way to login to the server.
For example: You may not have any special characters in the beginning of the password for an Ubuntu server when it is created, then you can not connect to it at all.
Q: I'm trying to use the API to create a server but it says that my key_pair name is not valid
A: In openstack key pairs are owned by the user that created the key pair and they can not be shared between users. This means that if a key pair is created by one user it will not be visible and can not be used by another user. This also means that if a key pair is created through citycontrolpanel, it can't be used by another API-user.
Q: Can I expand my system disk
A: When you create a server you can choose the size of the system disk. This size can not be changed ones created. Best practise is to keep vital data on an attached volume instead of on the system disk. The system disk is for the operating system. There are several benefits of keeping data on an attached volume instead of on system disk. A volume can be moved between servers, so if a server should run into issues or needs to be taken offline for some reason you can simply connect the volume to a replacement server. The size of the volume can be extended whenever you want. You can always increase the size of a volume, but not decrease. Should you still end up with a scenario when you need more system disk space your best option is to create it as a new server to replace the old one:
- Take snapshot of the server
- Start a new server from that snapshot with a larger system disk
Q: How do I install a server from an ISO?
A: The best way is to create a new image from the installed ISO and use that to create servers. This is done with the following steps:
- Create a private image, choose ISO as type
- Create a server from the ISO (boot source: private image, choose the created iso image). This will create a new server with the ISO attached as a CD-ROM and create a new volume with the specified size and mount it to the created server.
- Install the server operating system from the ISO by connecting to the server via VNC (connect-tab on server). This will install the operating system on the attached volume.
- Delete the server (the volume is not deleted)
- Create an image from the volume. (Volume list, click action button on the volume and choose create image)
- Create a new server from the newly created image
Q: Can you tell us which are the links? in-out bandwidth from each datacenter?
A: Our data centers are connected through wavelength connections and we don’t separate each data center from a bandwidth perspective. We have multiple high capacity transit connections from different service providers at each site, and are also connected to Internet Exchange Points. Traffic can enter at any of our transit providers or Internet Exchange Points and will then be transported inside our network to the right destination. As our network change rapidly and capacity is added all the time we don’t specify the exact amount of transit capacity. What are your requirements? Contact our support for more information or our salesdepartment.
Q: How do i become root in my server?
A: When you log in, it's like a normal user, enter "sudo -i" and enter the password for your normal user again.
This will make you root on your VM.
Q: Unable to boot from the ISO image?
1.) I will have to make a new server from my own ISO image with OpenBSD 5.8, so I use the "private image". Everything works fine, but i can not find where i set up the server will not choose " boot from" the ISO image. Previously there was a setting for boot order under "Advanced Options", but i can not find it in the new interface.
2.) In the VNC panel the keyboard is mapping badly from a MacBook Air with Swedish keyboard layout. Among other things, i can not find a hyphen (-), which makes it difficult to make the installation as i want it.
1.) There is no longer any advanced options for the boot current ISO mounts. What you can do is to create a snapshot on the server after you have installed it, and then spins up a new machine from the snapshot. It will then not boot from a CD.
You can delete the snapshot and the old serve after you've created the new.
2.)Once you are logged in by VNC, you can try using the command "loadkeys" and then upload, for example us, to get a different layout.
The entire command is: loadkeys us