Link: https://openstack.nimeyo.com/31835/?show=68695#c68695
From: buptzhoutian
The most likely reason : You configured your mysql connection in the [api_database] , not [database]
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinf
Hi,
I have implemented Liberty setup.I need to know the Open source billing
tools available for Liberty release
Thanks Regards
Pallavi.Shete
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.ope
Can you configure your openstack install to boot from hard drive after
installing via PXE boot and Fuel?
Do i just change the BIOS settings to boot from Hard Drive first?
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Pos
On 12/14/2015 12:40 PM, pallavi shete wrote:
I have implemented Liberty setup.I need to know the Open source billing
tools available for Liberty release
You should have a look on CloudKitty.
https://github.com/openstack/cloudkitty
---snip---
CloudKitty aims at filling the gap between metrics
On 12/08/2015 09:33 PM, Laohu wrote:
I know there is latency in step 1 & 2, but could not find documents on
state(status) map of instance, volume and IP address.Can experts point
me to right place to check or provide advice on how to ensure successful
remote connection to a newly created instance
Progress but new issues.
After changing the above OS_USERNAME envron variable to "admin" the
error no longer is "invalid User" but now is "Could not find project"
So, specific question(s):
Does stack.sh set up a default project?
Is there a specific command to display and list configured projects?
Hi John,
yes, it should be enough to just change BIOS settings to boot from Hard
Drive.
If nodes continue to use PXE, Fuel will be just replying that in order to
continue booting, those should just look for localboot (hard drive). If you
power Fuel Master off, nodes will not find PXE server and wi
Hi All,
Currently, it is possible to create unlimited number of resource like
bay/pod/service/. In Magnum, there should be a limitation for user or
project to create Magnum resource,
and the limitation should be configurable[1].
I proposed following design :-
1. Introduce new table magnum.quotas
Hi,
I am trying to launch instance on 2 node Openstack system.
Controller and compute both nodes are on Ubuntu Server 14.04 / intel i5
processor
while booting instance through command prompt as well as from dashboard,
I am getting following error in nova-compute.log
*qemuMonitorOpenUnix : 306 : f
Can we have nested project quotas in from the beginning ? Nested projects are
in Keystone V3 from Kilo onwards and retrofitting this is hard work.
For details, see the Nova functions at
https://review.openstack.org/#/c/242626/. Cinder now also has similar
functions.
Tim
From: Vilobh Mes
10 matches
Mail list logo