2016-06-09 20:58:43 -0500 commented answer How to properly reboot a machine running devstack.sh? rejoin-stack.sh is removed in the latest version. What's the properway to restart/shutdown 2016-06-02 00:40:38 -0500 answered a question error during chunked upload - can't create large glance images I finally worked out the problem. I believe if you put the below settings in your devstack/local.conf SWIFT_LOOPBACK_DISK_SIZE=100G [[post-config|${SWIFT_CONF_DIR}/swift.conf]] [swift-constraints] max_file_size = 21474836482 reinstall openstack ./stack.sh ./unstack.sh, You should now be able to upload image under 20GB. 2016-03-04 20:46:47 -0500 commented answer restart openstack service thank you, this one worked :). I ssh as stack user, everything worked fine 2016-03-04 01:04:48 -0500 commented answer tempest initialization fails while devstack installation. can this be changed in setup.cfg instead? then we run the ./stack.sh installation script file 2016-02-26 00:39:07 -0500 commented answer Erros devstack stable/liberty install behind proxy self-signed ssl certificate glad it worked ;) I still had some problem getting the tempest (Integration testing tool) to work (so I disabled the tempest service in order to get openstack install successfully), if I put the export pip_cert=/etc/ssl/certs/ca-certificates.crt in side the stack.sh, would that help? :) 2016-02-22 06:32:38 -0500 answered a question error during chunked upload - can't create large glance images I installed openstack using devstack, just wondering, how would I be able restart individual components in this case? I don't find the glance-api or the glance-registry service  stack@mep-openstack1:/etc/glance$ sudo service --status-all [ + ] apache2 [ + ] apparmor [ ? ] cntlm [ ? ] console-setup [ + ] cron [ ? ] cryptdisks [ ? ] cryptdisks-early [ - ] dbus [ ? ] dns-clean [ + ] ebtables [ + ] friendly-recovery [ - ] grub-common [ ? ] irqbalance [ ? ] killprocs [ ? ] kmod [ + ] libvirt-bin [ + ] memcached [ ? ] mysql [ ? ] networking [ ? ] ondemand [ + ] open-iscsi [ ? ] pppd-dns [ - ] procps [ + ] rabbitmq-server [ ? ] rc.local [ + ] resolvconf [ + ] rsync [ + ] rsyslog [ ? ] screen-cleanup [ ? ] sendsigs [ - ] ssh [ - ] sudo [ ? ] sysfsutils [ + ] tgt [ + ] udev [ ? ] umountfs [ ? ] umountiscsi.sh [ ? ] umountnfs.sh [ ? ] umountroot [ - ] urandom [ - ] x11-common [ ? ] zfs-fuse  I also can't do ./unstack.sh, ./stack.sh, because if I do this, all my existing data will be wiped. is there anyway to specify the swift_store_large_object_size in the local.conf, before the ./stack.sh installation. 2016-02-15 00:05:56 -0500 received badge ● Enthusiast 2016-02-14 21:44:12 -0500 commented answer cannot remove volume Thanks a lot for the guide. Cinder delete or force-delete didn't work for me. But I managed to resolve the problem by modifying the corresponding volume's status = "available", attachment_status="detached" in cinder.volumes and cinder.volume_attachment. Then cinder delete worked :) 2016-02-14 21:42:06 -0500 received badge ● Supporter (source) 2016-02-08 21:15:03 -0500 received badge ● Editor (source) 2016-02-08 10:08:07 -0500 answered a question Erros devstack stable/liberty install behind proxy self-signed ssl certificate most likely your corporate fire wall have captured the ssl certifcate and reissued another certficate of their own back to your machine. (your distro of linux machine is doing the right thing, because your corporation is actually pretending to be owner of the site (which the installer is trying to download the package from), when they are actually not, what this means is that your corporation proxy servers can decrypt and spy on your requests to the sites). What you can do is the below ask your corporation for the certficate (which they always capture and issue back to you), you should also be able to physically save this certificate as a crt file. When you visit any https website (within your corporations network) in a browser, and use your browser to download the certficate file as a crt file. Install (import) the certifcate to your Linux Machine, you can follow instructions on this site (http://kb.kerio.com/product/kerio-con...) you have to do two things here  3.1 first thing - you have to make couple changes to the files in several files to specify the certificate location  Details on the files to change to specify the certificate location Assuming you've already set up your proxy correctly devstack/inc/python: line 151-157, insert "--cert= \" after "$cmd_pip$upgrade \", in my case, my is /etc/ssl/certs/ca-certificates.crt devstack/inc/python: line 165-171, insert "--cert= \" after "$cmd_pip$upgrade \", in my case, my is /etc/ssl/certs/ca-certificates.crt devstack/tools/install_pip.sh: line 80, change this line to something like sudo -H -E python $LOCAL_PIP --cert= -c$TOOLS_DIR/cap-pip.txt , in my case, my is /etc/ssl/certs/ca-certficates.crt Note, some of the files might be downloaded files during installation, if they are, make the changes after they are downloaded (if none of these files are downloaded files during installation, good it just makes life easier), also if your installation is using python3, you should make these similar changes to python3 locations in the files, they should be right next to the above locations specified 3.2 second thing - create a configuration file for pip at location ~/.pip/pip.conf In the pip.conf file you need to specify the location of the ssl certificates. it should look something like below  [global] cert = For me the is /etc/ssl/certs/ca-certificates.crt