<br><br>W dniu pon, mar 25, 2013 o 4:36 ,nadawca Ian Booth <ian.booth@canonical.com> napisał:<br> <blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">H</div></blockquote><div><br></div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">One possible reason for any difference is that the web page you are looking at was written for Python Juju. Go Juju doesn't deliberately use different config settings but there might be subtle differences. default-image-id: "75845" The image id above from juju init is for a recent Precise 12.04 64 bit server. The 8419 image id on the web page is for a deprecated image, so the difference there is that the web page is out of date. A general comment - image ids are used right now because work to support constraints is not quite ready for Openstack deployments. The need for explicit image ids will disappear as soon as the constraints work is finalised. The default series config setting for Go Juju is commented out in the juju init generated config, but the purpose of the field is currently the same as for Python Juju. Work is being done in Go Juju to change how series is handled, and this will be documented in the relevant release notes</div></blockquote><div><br></div>I only meant that image-id implies series. If one is specified then the other is useless. It is also unclear which takes precendence when both are used.<br><div><br></div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;"> <blockquote> 3) Juju gives a very confusing error message if object storage is not activated and activated in the right region </blockquote> We'll see what can be done to improve the error message. Do you have an example of the message you are referring to?</div></blockquote><div><br></div><div>I don't have the error message anymore (and I cannot deactivate the object store from the web console) but I would expect something like</div><div> "you need to activate object store for <region> to use juju: <link to where this can be done>. Since this is something that each user of HP cloud will bump into (unless they activate everything up front, which I would not do) it should be handled better.</div><div><br></div><div><br></div><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;"> Yes, this is a known limitation. See bug 1135335. <blockquote> 5) Region names seem to have changed as compared to our documentation examples </blockquote> Do you have a specific example? The web page refers to region "az-1.region-a.geo-1" and this is the same as I have in my OS_REGION_NAME env variable. </div></blockquote><div><br></div><div>Ah, more confusion, see below</div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;"> <blockquote> 6) the purpose of some fields feels too cryptic. I don't really know what 'tenant-name' is for. </blockquote> >From the juju init output: # Usually set via the env variable OS_TENANT_NAME, but can be specified here # tenant-name: <your tenant name> Where to get your tenant name is shown the the web page. </div></blockquote><div><br></div><div>Replace TENANT with FROZBONICATOR. It still doesn't tell you how this field is used. I guess there are two parts of configuration that juju requires:</div><div><br></div><div>1) Boring stuff that "just has to be defined" that is not real configuration, just fixed-per-user blob</div><div>2) Configuration that users want to change and thus need to understand.</div><div><br></div><div>Currently TENANT falls under 1) but I suspect it's 2) in disguise </div><div><br></div><div>As a user I still don't understand what the tenant is or how it can be used to gain something. Since I apparently can create them on <a href="https://account.hpcloud.com/projects">https://account.hpcloud.com/projects</a> can those be just called "projects"?</div><div><br></div><div>What Juju can do better here: the automatically generated configuration example could briefly explain what the tenant/project field is for along with a link to juju docs that explain the topic in depth and give examples on when a user might want to create additional projects.</div><div><br></div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;"><blockquote> 7) Bootstrap fails like this: zyga@g580:~$ juju bootstrap --upload-tools error: cannot start bootstrap instance: cannot find image satisfying constraints: failed to get list of flavours, caused by: no endpoints known for service type: compute </blockquote> This indicates the region is not set correctly.</div></blockquote><div><br></div>You were right. <div><br></div><div>This is totally confusing though and I don't understand why that value is correct, compare:</div><div><br></div><div>From <a href="https://account.hpcloud.com/account/api_keys">https://account.hpcloud.com/account/api_keys</a></div><div><br></div><div>There are seven groups of service endpoints:</div><div>1) identity</div><div>2) block storage</div><div>3) CDN</div><div>4) compute</div><div>5) image management<br><div>6) networking</div><div>7) object storage</div><div><br></div><div>In each group there are multiple URLs apparently grouped by regions:</div><div><br></div><div>* region-a.geo-1 </div><div>* region-b.geo-1 </div><div>* az-1.region-a.geo-1</div><div><br></div><div>The value with "az-1." prefix is only used by block storage, compute and networking.</div><div><br></div><div>As a user I really expected something tangible like what Amazon currently provides (geographical location). Presumably "az-1" is availability zone 1 but I'm just guessing. How that compares to region a and b is beyond me.</div><div><br></div><div>What Juju can do better here: have working documentation that works out of the box</div><div>What HP could do better here: the UI is confusing. I realize that some of those values are very much for developers to use but perhaps some partnership "this is how to use juju with your account" could be possible here.</div><div><br></div><div>So with the region fix, I apparently can bootstrap. Going to <a href="https://console.hpcloud.com/compute/az-1_region-a_geo-1">https://console.hpcloud.com/compute/az-1_region-a_geo-1</a> I can see one machine running.</div><div><br></div><div>Issuing $ `juju status` fails though:</div><div><br></div><div>zyga@g580:~/.juju$ juju bootstrap --upload-tools</div><div>zyga@g580:~/.juju$ juju status</div><div>error: no reachable servers</div><div>zyga@g580:~/.juju$ juju status</div><div>error: failed to get list of server details, caused by: <a href="https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/35370665361422/servers/detail?name=juju-hpcloud-.%!A">https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/35370665361422/servers/detail?name=juju-hpcloud-.%!A</a>(string=failed executing the request), caused by: Get <a href="https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/35370665361422/servers/detail?name=juju-hpcloud-.%2A">https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/35370665361422/servers/detail?name=juju-hpcloud-.%2A</a>: remote error: handshake failure</div><div><br></div><div>Thanks</div></div><div>ZK</div>