| bshephar | Hey palaueb. Yeah, so you can do what Steve suggests there by creating a template with everything you need. Then calling that template as part of a resource group which would create VM's with associated VolumeAttachments | 03:00 |
|---|---|---|
| *** ysandeep|out is now known as ysandeep | 05:30 | |
| palaueb | Yeah, I did that, now our nova is returning me an error about the names, let's see what my sysadmin tells about that message | 07:12 |
| palaueb | Thanks a lot for your help and support | 07:12 |
| *** ysandeep is now known as ysandeep|lunch | 08:02 | |
| bshephar | No worries. I uploaded that video as well btw: https://youtu.be/OiQXs33SpBY | 08:57 |
| bshephar | Just covered what we spoke about with some details around using the %index% option to create vm-0, vm-1, vm-2, etc. A little bit about finding error messages, looking at nested stacks. Re-using templates with different environment files and scaling existing stacks | 08:58 |
| *** ysandeep|lunch is now known as ysandeep | 09:12 | |
| palaueb | Oh!! thanks! i will check it just right now | 10:05 |
| palaueb | meanwhile, I'm getting a consistent error that I can't solve: Resource Create Failed: Badrequest: Resources.Server Instance: An Invalid 'Name' Value Was Provided. The Name Must Be: Printable Characters. Can Not Start Or End With Whitespace. (Http 400) (Request-Id: Req-xxxx) | 10:06 |
| palaueb | but I just set this to try to debug: name: "SERVERNAME-test" | 10:06 |
| palaueb | I have checked nova source for our version | 10:07 |
| palaueb | function valid_name_regex = ValidationRegex | 10:08 |
| palaueb | resources.server_instance: An invalid \'name\' value was provided. <- this makes no sense for me right now | 10:23 |
| palaueb | server_name vxsys-test-0%index%env0%index% | 10:40 |
| palaueb | I can't see why that's not a valid name | 10:41 |
| palaueb | It really does not create the resource, I can't query os to ask what happened because the Server is not created ... | 10:45 |
| *** ysandeep is now known as ysandeep|brb | 12:40 | |
| *** ysandeep|brb is now known as ysandeep | 13:10 | |
| *** ysandeep is now known as ysandeep|out | 15:25 | |
| palaueb | it seems to have a problem with availability_zone ... weird behavior | 15:40 |
| palaueb | ok, we have found the problem. It seems that the availability zones for compute and volumes are not the same, I have to use nvme for volumes and nova for compute, but the error returned by nova is about the server name .... WEIRD | 15:53 |
| palaueb | I suppose this only happens on queens version | 15:53 |
| *** ysandeep|out is now known as ysandeep | 16:33 | |
| *** ysandeep is now known as ysandeep|out | 17:11 | |
| bshephar | Hey palaueb, I'll have a look at the name you used. I was using a RHOSP13 environment which is Queens in that video as well. I'll confirm the name there | 21:29 |
| bshephar | palaueb: Hmm, seems to work fine with that name: | 22:09 |
| bshephar | $ openstack server list --name vxsys -f yaml -c Name -c Status | 22:09 |
| bshephar | - Name: vxsys-test-02env02 | 22:09 |
| bshephar | Status: ACTIVE | 22:09 |
| bshephar | - Name: vxsys-test-01env01 | 22:09 |
| bshephar | Status: ACTIVE | 22:09 |
| bshephar | parameter_defaults: | 22:09 |
| bshephar | ServerName: 'vxsys-test-0%index%env0%index%' | 22:09 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!