Thank you all very much for the replies!
Gene
On 14-05-13 06:37 PM, Ruben S. Montero wrote:
> Yes, there maybe a problem. There won't be nothing to stop the
> scheduler from allocating the VM if it's resumed. That's the reason
> for accounting the capacity even if you are not actually using it,
>
If you look into those init scripts (under /etc/one-context.d) you will
figure out the details.
In my context setting (4.4.1), I have both SET_HOSTNAME and DNS_HOSTNAM
and it works well.
CONTEXT
NETWORK YES
TOKEN YES
SET_HOSTNAME$UNAME$VMID
SEARCH_DOMAIN ***
After I setup a proxy server (ngnix) before sunstone server on master.
>From Sunstone UI (192.168.100.10), I can not change zone to "zone1".
Other functions work well from sunstone UI, but changing "zone".
*
If I remove the proxy server, and access directly to sunstone
server: 192.168.1
All,
I wonder if anyone experienced the same weird error -- VMs shutdown
themselves? (in my environment, after running about 2 minutes)
The VMs from same template/image run well on master zone.
Anyone has any ideas?
Log from sunstone console. (other logs are clean)
Fri Aug 22 14:56:12 2014 [Z100
Sorry that I missed some important information:
OpenNebula 4.8
Nodes and frontend server are all RHEL7.0
Hypervisor: KVM
Thanks,
Gene
On 14-08-22 03:13 PM, Liu, Gene wrote:
> All,
>
> I wonder if anyone experienced the same weird error -- VMs shutdown
> themselves? (in my enviro
-
5 one-7 running
On 14-08-22 03:16 PM, Liu, Gene wrote:
> Sorry that I missed some important information:
>
> OpenNebula 4.8
> Nodes and frontend server are all RHEL7.0
> Hypervisor: KVM
>
> Thanks,
> Gene
>
> On 14-08-22 03
Thanks Daniel!
Could you please specify "how"?
Gene
On 14-08-25 06:16 AM, Daniel Molina wrote:
> "ZONE_NAME" http header
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Thank you Carlo!
It works after those two parameters setting.
Gene
---
server {
listen 12.34.56.78:80;
server_name xx.yy.alcatel-lucent.com;
underscores_in_headers on;
location / {
proxy_set_headerHost $host;
proxy_pass_reque
FYI. and a follow-up.
After I reboot the front-end server (slave zone) and computing nodes,
the problem is gone.
-- Gene
On 14-08-22 03:20 PM, Liu, Gene wrote:
> I just found that these VMs are "running" still on the nodes. Its
> weird that OpenNebula changed their status to &qu
FYI.
We added virtual serial console feature on our private cloud via adding
and modifying a few back-end scripts and UI change a little bit.
Gene
On 14-11-19 07:37 AM, Vassilis Vatikiotis wrote:
> Is it possible to setup both noVNC and a serial console?
>
> I've already setup a template for seri
Hi Everyone,
Anyone had ever encounter an issue about VM stat changes to "POWEROFF" a
few minutes (2 ~ 3 minutes) after "RUNNING"?
The actual problem is that the "POWEROFF" stat is incorrect as the VM is
actually running on the computing node. If you try to "boot" it back, it
will failed as that
11 matches
Mail list logo
