#solum

hi ... i am trying to run the solum dev setup from here -> https://solum.readthedocs.org/en/latest/getting...

but when i try to run the solum client it asks for the os_username, os_password, os_tenant etc.. etc.. i vagrant ssh'ed into the running virtualbox using "vagrant ssh devstack" i dont know what values i must provide to solum client... its not document on the rtd website can someone help me figure where i have missed something ? another approach i took was to "vagrant ssh" and run stack.sh directly fomr within the devstack directory

hi

need some help with https://github.com/rackerlabs/vagrant-solum-dev...

i get an error when I run devstack/stack.sh with an n-cpu failure ... etc.

can someone help me fix this ?

test123user: hi

hi

test123user: thanks for pinging here

u/w

test123user: give me a minute

sure np

going to unstack and run without SOLUM_IMAGE_FORMAT=vm

test123user: sorry, have been a bit tied up this morning..

test123user: please set SOLUM_IMAGE_FORMAT=docker

let me give some context as to what i am trying to do

test123user: can you verify for me some things

test123user: oh sure, that will help

so i was reading your folks excellent blog and online videos

so i thot i cd learn me some solum

looks like things are different when the rubber hits the road

anyway.............

so i tried the sample python app demo and was able to do all the steps... however,

when i tried to deploy, i got an error (no surprise !!)

test123user: actually getting a working devstack environment has improved considerably from before

test123user: i will help you get a successfully deployed app

test123user: Ablu tried it yesterday, who is a new user as well

one mo... let me get the link (i think) i used for the demo

yes, that will be good.. may be that link has old info

i got it working in the end

this is what i last referred to....

not all links are old... just some have parts which dont work any more ATPIT

in fact the troubleshooting section has the exact output of what i got as an error

upto the "nova show blabla" part at the end

of course the uuid values were different but the error messages were similar

test123user: thanks for this info

test123user: I will go through that link and fix anything that is old

test123user: for now, the latest examples that should work are here:

test123user: https://github.com/openstack/solum/tree/master/...

ok will test it out.... anything else which I need to note/keep-in-mind ?

test123user: can you tell me what is your development environment?

btw do I need to fix the stack.sh error first ?

are you using vagrant or you already have a devstack and using that?

i had chosen to ignore it since all steps worked until i hit "solum app deploy foobar"

yes i am on vagrant + virtualbox

test123user: ok.. so few points

1) if you have vagrant vm in which you were able to create a languagepack, then that is good.. you can continue working with that vm without destroying it

2) the n-cpu failure that you saw is something that needs to be handled for 'solum app deploy' work.

3) the way to resolve the n-cpu failure is to follow the steps outlined in step 7 of https://wiki.openstack.org/wiki/Solum/solum-dev... Vagrant setup

4) once you have updated /etc/nova/nova.conf as indicated in that step, all you have to do is restart the nova services which have failed (which most likely will be n-cpu)

after that, you can try 'solum app deploy' and that should work

quick command to restart nova services ?

that is all you need to keep in mind

test123user: sure

also to check for various solum services, any quick commands or scripts ?

ty

test123user: typically the way I do is, login to the screen session (screen -x stack) and then navigate to the screens of each of the nova services, check if they have failed, and if they have, just re-issue the last command from that screen

test123user: there is no script as such to check if openstack services are up or not.. but

fine... i am not a big fan of screen, but i guess there is a reason e.., re-issuing last command etc..

following command is what I use: ps -eaf | grep n-*

ps -eaf | grep solum-*

i tried the 2nd one... yielded nothing

so i guess i will start over with step 7 from your steps and also ensure i turn on docker for solum image format

test123user: wait

test123user: you said you tried to grep for solum services and nothing showed up?

test123user: if that is the case, then it means that none of the solum services have started up correctly

if so,

you will have to unstack and stack again

before you do that though, can you verify something for me

in your devstack directory, can you grep for 'enable_plugin solum git://git.openstack.org/openstack/solum';

in local.conf

essentially, check if your local.conf matches with https://github.com/devdattakulkarni/solum-prove...

@devkulkarni I have already unstacked and going to set the solum image format to docker

brb

test123user: ok

test123user: before you stack, just make sure that the local.conf in devstack directory is what I had outlined above ^^

test123user: we solum weekly irc meeting in 15 or so minutes (1700 UTC) in openstack-meeting-3

if you have time, you can join us there

I have an internal meeting right after that for an hour

I will be available at 1900 UTC

sure np... i will check back here then ... thanks so much

test123user: cool.. I would help you with getting the env for using/experimenting with solum

feel free to ping me with any questions you may have

team, we have our weekly irc meeting in 15 minutes in openstack-meeting-3

here is the agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#...

brb

sorry small question

is there a way to do this in debian... ?

ie run devstack from within a debian vagrant vbox ?