Hello, A few folks give me some suggestion, and I followed it, it seems that the problem is not solved yet, anyone can tell what steps here is not correct?
openstack@ubuntu:~$ keystone-manage db_sync openstack@ubuntu:~$ openssl rand -hex 10 2c3a6bb5b3b8880f44f2 openstack@ubuntu:~$ sudo vi /etc/keystone/keystone.conf [sudo] password for openstack: openstack@ubuntu:~$ service keystone restart stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.6" (uid=1000 pid=4110 comm="stop keystone ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") start: Rejected send message, 1 matched rules; type="method_call", sender=":1.7" (uid=1000 pid=4107 comm="start keystone ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") openstack@ubuntu:~$ sudo service keystone restart keystone stop/waiting keystone start/running, process 4116 openstack@ubuntu:~$ export OS_SERVICE_TOKEN=2c3a6bb5b3b8880f44f2 openstack@ubuntu:~$ export OS_SERVICE_ENDPOINT=http://controller:35357/v2.0 openstack@ubuntu:~$ keystone tenant-create --name=admin --description="Admin Tenant" An unexpected error prevented the server from fulfilling your request. (ProgrammingError) (1146, "Table 'keystone.token' doesn't exist") 'SELECT token.id AS token_id, token.expires AS token_expires, token.extra AS token_extra, token.valid AS token_valid, token.user_id AS token_user_id, token.trust_id AS token_trust_id \nFROM token \nWHERE token.id = %s' ('2c3a6bb5b3b8880f44f2',) (HTTP 500) openstack@ubuntu:~$ sudo keystone tenant-create --name=admin --description="Admin Tenant" Expecting an auth URL via either --os-auth-url or env[OS_AUTH_URL] Best Regards! Min Wang Software Engineer-Cloud Service min.wa...@hp.com -----Original Message----- From: Fox, Kevin M [mailto:kevin....@pnnl.gov] Sent: Wednesday, April 16, 2014 9:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [heat] computed package names? Different distro's move the binaries and services too. ubuntu/debian does: /usr/sbin/apache2, not httpd. The service is also named apache2, not httpd. So, I think distro specific sets of packages are somewhat unavoidable. Now, this use case might be a good case for supporting: https://blueprints.launchpad.net/heat/+spec/intrinsics https://blueprints.launchpad.net/heat/+spec/aws-novalue Amazon finally caved in and implemented these. I think heat needs them too. Is it possible to implement those with the new plugin function framework? If so, I might be willing to take a stab at it if I can find a bit of time. Thanks, Kevin ________________________________________ From: Zane Bitter [zbit...@redhat.com] Sent: Wednesday, April 16, 2014 8:39 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [heat] computed package names? On 16/04/14 05:53, Thomas Spatzier wrote: > IMO, it would be desirable to not have things like yum or apt appear > in the template explicitly. For many packages it seems like at least > the top level package names (not including distro specific versioning > strings) are equal across distros so when specified in a template it > should be possible for a software deployment hook (which can be distro > specific) to figure out how to install the package. I think this thread demonstrates the opposite: package names can be different even among closely-related distributions (Fedora vs. RHEL) - or even versions of the same distribution (Fedora 17 vs. 18). And while Ubuntu is derived from Debian (and thus most apt packages are likely to share package names), there's no reason whatsoever to expect e.g. OpenSUSE to have the same package names as Fedora, despite both being based on RPM. Brian Aker once suggested to me a scheme based on the path to the thing you want installed: e.g. you request /usr/bin/httpd and the agent uses "yum provides" or the apt equivalent to install the appropriate package. That's an idea that might work better, although paths are by no means standardised across distros either. In any event, though, my impression is that we are trying to get out of the cfn-init business as much as possible and leave the task to some combination of custom images, software config and configuration management. Hopefully someone will correct me if that impression is inaccurate... cheers, Zane. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
