From a117e9ab24b7651878e8133ef4a9a823ab454ac0 Mon Sep 17 00:00:00 2001 From: James Page Date: Tue, 13 Nov 2018 13:57:39 +0000 Subject: [PATCH] Rename snap from microstack to openstack --- README.md | 46 +++++++++++++++++++++++----------------------- snapcraft.yaml | 8 ++++---- 2 files changed, 27 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 971d8ca..e1e76ae 100644 --- a/README.md +++ b/README.md @@ -1,32 +1,32 @@ -# microstack +# openstack -[![Snap Status](https://build.snapcraft.io/badge/CanonicalLtd/microstack.svg)](https://build.snapcraft.io/user/CanonicalLtd/microstack) +[![Snap Status](https://build.snapcraft.io/badge/CanonicalLtd/openstack.svg)](https://build.snapcraft.io/user/CanonicalLtd/openstack) OpenStack in a snap that you can run locally on a single machine! -`microstack` currently provides Nova, Keystone, Glance, Horizon and Neutron OpenStack services. +`openstack` currently provides Nova, Keystone, Glance, Horizon and Neutron OpenStack services. ## Installation -`microstack` is frequently updated to provide the latest stable updates of the most recent OpenStack release. The quickest was to get started is to install directly from the snap store. You can install `microstack` using: +`openstack` is frequently updated to provide the latest stable updates of the most recent OpenStack release. The quickest was to get started is to install directly from the snap store. You can install `openstack` using: ``` -sudo snap install microstack --classic --edge +sudo snap install openstack --classic --edge ``` ## Accessing OpenStack -`microstack` provides a pre-configured OpenStack CLI to access the local OpenStack deployment; its namespaced using the `microstack` prefix: +`openstack` provides a pre-configured OpenStack CLI to access the local OpenStack deployment; its namespaced using the `openstack` prefix: ``` -microstack.openstack server list +openstack.openstack server list ``` -You can setup this command as an alias for `openstack` if you wish (removing the need for the `microstack.` prefix): +You can setup this command as an alias for `openstack` if you wish (removing the need for the `openstack.` prefix): ``` -sudo snap alias microstack.openstack openstack +sudo snap alias openstack.openstack openstack ``` Alternatively you can access the Horizon OpenStack dashboard on `http://127.0.0.1` with the following credentials: @@ -38,25 +38,25 @@ password: keystone ## Booting and accessing an instance -`microstack` comes preconfigured with networking and images so you can get starting using OpenStack as soon as `microstack` is installed; to boot an instance: +`openstack` comes preconfigured with networking and images so you can get starting using OpenStack as soon as `openstack` is installed; to boot an instance: ``` -microstack.openstack server create --flavor m1.small --nic net-id=test --image cirros my-microstack-server +openstack.openstack server create --flavor m1.small --nic net-id=test --image cirros my-openstack-server ``` To access the instance, you'll need to assign it a floating IP address: ``` -ALLOCATED_FIP=`microstack.openstack floating ip create -f value -c floating_ip_address external` -microstack.openstack server add floating ip my-microstack-server $ALLOCATED_FIP +ALLOCATED_FIP=`openstack.openstack floating ip create -f value -c floating_ip_address external` +openstack.openstack server add floating ip my-openstack-server $ALLOCATED_FIP ``` -and as you would expect, `microstack` is just like a full OpenStack Cloud and does not allow ingress access to the instance by default, so next enable SSH and ping access to the instance: +and as you would expect, `openstack` is just like a full OpenStack Cloud and does not allow ingress access to the instance by default, so next enable SSH and ping access to the instance: ``` -SECGROUP_ID=`microstack.openstack security group list --project admin -f value -c ID` -microstack.openstack security group rule create $SECGROUP_ID --proto tcp --remote-ip 0.0.0.0/0 --dst-port 22 -microstack.openstack security group rule create $SECGROUP_ID --proto icmp --remote-ip 0.0.0.0/0 +SECGROUP_ID=`openstack.openstack security group list --project admin -f value -c ID` +openstack.openstack security group rule create $SECGROUP_ID --proto tcp --remote-ip 0.0.0.0/0 --dst-port 22 +openstack.openstack security group rule create $SECGROUP_ID --proto icmp --remote-ip 0.0.0.0/0 ``` once this is complete you should be able to SSH to the instance: @@ -65,20 +65,20 @@ once this is complete you should be able to SSH to the instance: ssh cirros@$ALLOCATED_FIP ``` -Happy `microstack`ing! +Happy `openstack`ing! -## Stopping and starting microstack +## Stopping and starting openstack -You may wish to temporarily shutdown microstack when not in use without un-installing it. +You may wish to temporarily shutdown openstack when not in use without un-installing it. -`microstack` can be shutdown using: +`openstack` can be shutdown using: ``` -sudo snap disable microstack +sudo snap disable openstack ``` and re-enabled latest using: ``` -sudo snap enable microstack +sudo snap enable openstack ``` diff --git a/snapcraft.yaml b/snapcraft.yaml index a5dd88a..5a29135 100644 --- a/snapcraft.yaml +++ b/snapcraft.yaml @@ -1,4 +1,4 @@ -name: microstack +name: openstack version: rocky summary: OpenStack on your laptop. description: | @@ -611,7 +611,7 @@ parts: # required to ensure that pathing to files etc works at # runtime # * is not used to avoid directory merge conflicts - snap/microstack/current/: ./ + snap/openstack/current/: ./ kvm-support: plugin: nil @@ -689,7 +689,7 @@ parts: # required to ensure that pathing to files etc works at # runtime # * is not used to avoid directory merge conflicts - snap/microstack/current/: ./ + snap/openstack/current/: ./ # MySQL mysql-server: @@ -770,7 +770,7 @@ parts: # required to ensure that pathing to files etc works at # runtime # * is not used to avoid directory merge conflicts - snap/microstack/current/: ./ + snap/openstack/current/: ./ ipset: source: http://ipset.netfilter.org/ipset-6.30.tar.bz2