Re: CloudStack 4.10 system VM without ip

2017-09-06 Thread Raja Pullela 
Hi Luis,

4.10 release does not support XenServer 7.2.  You will have to downgrade to 7.0.
Good luck!
Raja
Engineering, Accelerite
http://www.accelerite.com 




On 9/7/17, 6:43 AM, "Luis"  wrote:

>Hi
>I installed CS 4.10 with XenServer 7.2, after configuring CS the system VM 
>were created but without ip, is 4.10 ready for testing? I see it as ready on 
>the website but is not working for me.
>Greetings.
>
>Sent from Yahoo Mail on Android
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

CloudStack 4.10 system VM without ip

2017-09-06 Thread Luis 
Hi
I installed CS 4.10 with XenServer 7.2, after configuring CS the system VM were 
created but without ip, is 4.10 ready for testing? I see it as ready on the 
website but is not working for me.
Greetings.

Sent from Yahoo Mail on Android

Re: SystemVMs in Alert State | 4.7.1 release

2017-09-06 Thread Pierre-Luc Dion 
Hi Vijay,

What is the question, it look like a statement to help troubleshooting.

Le 31 août 2017 10:42 AM, "Vijay Sachdeva"  a
écrit :

Anyone who can reply to it please?

Thanks


*Vijay SachdevaConsultant - Cloud & Virtualisation*


A-4, LGF, C.R.Park, New Delhi - 110019
24x7 011-40551409 | M +918826699409 <+91%2088266%2099409>
www.indiqus.com

On 24-Aug-2017, at 6:30 PM, Vijay Sachdeva 
wrote:

Dear Team,

Has anyone gone through this, i.e. system VMs agent state never come up
until n unless you ping the management server IP from system VM. If you
don’t ping the same and when you run the “ssvm_check.sh” script it shows
not connectivity to port 8250.

The time you ping the management server IP and run the script, it connects
to port 8250 and agent state comes to UP state.

Thanks


*Vijay SachdevaConsultant - Cloud & Virtualisation*



A-4, LGF, C.R.Park, New Delhi - 110019
24x7 011-40551409 | M +918826699409 <+91%2088266%2099409>
www.indiqus.com

RE: CloudStack-UI 1.49.9 released on September 5, 2017

2017-09-06 Thread Imran Ahmed 
Excellent work . Please keep up!

-Original Message-
From: Ivan Kudryavtsev [mailto:kudryavtsev...@bw-sw.com] 
Sent: Wednesday, September 06, 2017 2:07 PM
To: users@cloudstack.apache.org
Subject: CloudStack-UI 1.49.9 released on September 5, 2017

Dear Community,

On September 5, 2017 we released CloudStack-UI version 1.49.9. This release
is a bugfix release. The key change in the release is the modification of
the version naming scheme, which was aligned with the Apache Cloudstack
versions releases. Thus, in version 1.49.9, the value of the numbers is:

   - "1" - responsible for the concept of the interface that is currently
   used;
   - "49" - responsible for compatibility with ACS, currently 4.9;
   - "9" - the current version of the CloudStack-UI product.

In the future, with the increase of releases lifetime, the fourth number
may appear. It will mean the minor version, and will be designed to reflect
changes related to bug fixes within the current version of the product.

In the current version of Apache Cloudstack 4.9.X we plan one more release
(1.49.10), in which the we will complete the migration to Material 2, fix
errors of medium and low level, and introduce number of interface
improvements related to usability and customization capabilities.

After release 1.49.10 we plan to switch the development environment to
CloudStack 4.10.0. The following releases will have names 1.410.X and will
be tested for compatibility only with the latest version of Apache
CloudStack 4.10.X. From release 1.410.X on we will move to a longer release
versions lifecycle, i.e. 1 month (current release cycle is 2 weeks).
Community
Message

Dear community member, we will be thankful if you

   - try the project and provide us with a feedback;
   - share the information about the project and the release in social
   media;
   - mark the GitHub repository  with
   star to support the project;
   - join LinkedIn group .


-- 
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/

CloudStack-UI 1.49.9 released on September 5, 2017

2017-09-06 Thread Ivan Kudryavtsev 
Dear Community,

On September 5, 2017 we released CloudStack-UI version 1.49.9. This release
is a bugfix release. The key change in the release is the modification of
the version naming scheme, which was aligned with the Apache Cloudstack
versions releases. Thus, in version 1.49.9, the value of the numbers is:

   - "1" - responsible for the concept of the interface that is currently
   used;
   - "49" - responsible for compatibility with ACS, currently 4.9;
   - "9" - the current version of the CloudStack-UI product.

In the future, with the increase of releases lifetime, the fourth number
may appear. It will mean the minor version, and will be designed to reflect
changes related to bug fixes within the current version of the product.

In the current version of Apache Cloudstack 4.9.X we plan one more release
(1.49.10), in which the we will complete the migration to Material 2, fix
errors of medium and low level, and introduce number of interface
improvements related to usability and customization capabilities.

After release 1.49.10 we plan to switch the development environment to
CloudStack 4.10.0. The following releases will have names 1.410.X and will
be tested for compatibility only with the latest version of Apache
CloudStack 4.10.X. From release 1.410.X on we will move to a longer release
versions lifecycle, i.e. 1 month (current release cycle is 2 weeks).
Community
Message

Dear community member, we will be thankful if you

   - try the project and provide us with a feedback;
   - share the information about the project and the release in social
   media;
   - mark the GitHub repository  with
   star to support the project;
   - join LinkedIn group .


-- 
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/

AW: Free capacity calculation within ACS

2017-09-06 Thread Jochim, Ingo 
Many thanks. We will check.

Regards,
Ingo

-Ursprüngliche Nachricht-
Von: Marc-Aurèle Brothier [mailto:ma...@exoscale.ch] 
Gesendet: Mittwoch, 6. September 2017 09:51
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS

Apparently in 4.2.0
https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7c54c76da9c16/setup/db/db/schema-410to420.sql

On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo 
wrote:

> Hello Marc-Aurèle,
>
> great. Didn't know that this parameter exists.
> Do you know in which ACS version this got introduced?
>
> Many thanks.
> Ingo
>
> -Ursprüngliche Nachricht-
> Von: Marc-Aurèle Brothier [mailto:ma...@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:15
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> Hi Ingo,
>
> You might want to look at the release period set in your installation:
> host.reservation.release.period. This release window time is there to 
> keep the capacity of stopped machines on a host for a certain time, 
> before releasing it, in case the machine has to start again soon 
> after. And most likely for other reason maybe in the advance 
> networking mode. So try to decrease this time window and check your capacity 
> after that.
>
> Marc-Aurèle
>
> On Tue, Sep 5, 2017 at 9:48 AM, Jochim, Ingo 
> wrote:
>
> > Hello all,
> >
> > within our CloudStack environment we like to park a couple of large 
> > machines in powered off state.
> > Those machines are demo machines which are needed only sometimes.
> > Those machines will get included in the capacity. That means we 
> > cannot build new machines even if there are free ressources on the 
> > hypervisors.
> > We don't want to solve it with overcommitment.
> > Is there a possibility to calculate free capacity without all 
> > powered off machines?
> >
> > Currently we have a dirty workaround. We created an offering with 1 
> > core and 1MB RAM and used that for all parked machines.
> > But this is not very nice.
> >
> > Any ideas or comments are welcome.
> > Thank you.
> > Ingo
> >
>

Re: Free capacity calculation within ACS

2017-09-06 Thread Marc-Aurèle Brothier 
Apparently in 4.2.0
https://github.com/apache/cloudstack/blob/f0dd5994b447a6097c52f405c7c7c54c76da9c16/setup/db/db/schema-410to420.sql

On Wed, Sep 6, 2017 at 9:42 AM, Jochim, Ingo 
wrote:

> Hello Marc-Aurèle,
>
> great. Didn't know that this parameter exists.
> Do you know in which ACS version this got introduced?
>
> Many thanks.
> Ingo
>
> -Ursprüngliche Nachricht-
> Von: Marc-Aurèle Brothier [mailto:ma...@exoscale.ch]
> Gesendet: Mittwoch, 6. September 2017 09:15
> An: users@cloudstack.apache.org
> Betreff: Re: Free capacity calculation within ACS
>
> Hi Ingo,
>
> You might want to look at the release period set in your installation:
> host.reservation.release.period. This release window time is there to
> keep the capacity of stopped machines on a host for a certain time, before
> releasing it, in case the machine has to start again soon after. And most
> likely for other reason maybe in the advance networking mode. So try to
> decrease this time window and check your capacity after that.
>
> Marc-Aurèle
>
> On Tue, Sep 5, 2017 at 9:48 AM, Jochim, Ingo 
> wrote:
>
> > Hello all,
> >
> > within our CloudStack environment we like to park a couple of large
> > machines in powered off state.
> > Those machines are demo machines which are needed only sometimes.
> > Those machines will get included in the capacity. That means we cannot
> > build new machines even if there are free ressources on the hypervisors.
> > We don't want to solve it with overcommitment.
> > Is there a possibility to calculate free capacity without all powered
> > off machines?
> >
> > Currently we have a dirty workaround. We created an offering with 1
> > core and 1MB RAM and used that for all parked machines.
> > But this is not very nice.
> >
> > Any ideas or comments are welcome.
> > Thank you.
> > Ingo
> >
>

AW: Free capacity calculation within ACS

2017-09-06 Thread Jochim, Ingo 
Hello Marc-Aurèle,

great. Didn't know that this parameter exists.
Do you know in which ACS version this got introduced?

Many thanks.
Ingo

-Ursprüngliche Nachricht-
Von: Marc-Aurèle Brothier [mailto:ma...@exoscale.ch] 
Gesendet: Mittwoch, 6. September 2017 09:15
An: users@cloudstack.apache.org
Betreff: Re: Free capacity calculation within ACS

Hi Ingo,

You might want to look at the release period set in your installation:
host.reservation.release.period. This release window time is there to keep the 
capacity of stopped machines on a host for a certain time, before releasing it, 
in case the machine has to start again soon after. And most likely for other 
reason maybe in the advance networking mode. So try to decrease this time 
window and check your capacity after that.

Marc-Aurèle

On Tue, Sep 5, 2017 at 9:48 AM, Jochim, Ingo 
wrote:

> Hello all,
>
> within our CloudStack environment we like to park a couple of large 
> machines in powered off state.
> Those machines are demo machines which are needed only sometimes.
> Those machines will get included in the capacity. That means we cannot 
> build new machines even if there are free ressources on the hypervisors.
> We don't want to solve it with overcommitment.
> Is there a possibility to calculate free capacity without all powered 
> off machines?
>
> Currently we have a dirty workaround. We created an offering with 1 
> core and 1MB RAM and used that for all parked machines.
> But this is not very nice.
>
> Any ideas or comments are welcome.
> Thank you.
> Ingo
>

Re: Free capacity calculation within ACS

2017-09-06 Thread Marc-Aurèle Brothier 
Hi Ingo,

You might want to look at the release period set in your installation:
host.reservation.release.period. This release window time is there to keep
the capacity of stopped machines on a host for a certain time, before
releasing it, in case the machine has to start again soon after. And most
likely for other reason maybe in the advance networking mode. So try to
decrease this time window and check your capacity after that.

Marc-Aurèle

On Tue, Sep 5, 2017 at 9:48 AM, Jochim, Ingo 
wrote:

> Hello all,
>
> within our CloudStack environment we like to park a couple of large
> machines in powered off state.
> Those machines are demo machines which are needed only sometimes.
> Those machines will get included in the capacity. That means we cannot
> build new machines even if there are free ressources on the hypervisors.
> We don't want to solve it with overcommitment.
> Is there a possibility to calculate free capacity without all powered off
> machines?
>
> Currently we have a dirty workaround. We created an offering with 1 core
> and 1MB RAM and used that for all parked machines.
> But this is not very nice.
>
> Any ideas or comments are welcome.
> Thank you.
> Ingo
>