Re: Survey “Building an autonomic cloud for you”

2017-03-28 Thread Lucas Berri Cristofolini 
Hey guys,

Once again I'd like to thank everyone who has answered the survey so far!

Now, just in case you are wondering what this Autonomiccs thing is all
about, we've prepared a small video demonstration of what we are working
on. It's a bit rough around the edges but it manages to showcase what is
currently available through our platform:
https://www.youtube.com/watch?v=dj5DO4Dcf98

More data is always welcome, and you can take our short survey right here:
https://goo.gl/forms/vvu0665FfKujn6gP2 ;)

Cheers,
Lucas

On Mon, Mar 20, 2017 at 7:35 PM, Lucas Berri Cristofolini <
lucascristofol...@gmail.com> wrote:

> Dear CloudStack community,
>
> I'd like to thank those of you who've answered the survey so far.
> However, we need more data; the questionnaire should take no more than 3
> minutes to fill out and is available here: https://goo.gl/forms/vvu0665Ff
> Kujn6gP2.  All of the answers are confidential (no company will be
> identified in none of our analysis). These data are crucial to focus our
> development efforts on features that attend your needs.
>
>
> To give you a taste of what our platform can do, our agents can,
> autonomously, execute virtual machines balancing or consolidation of your
> cloud system. For instance, according to our experiments, it is possible to
> save up to 30% of energy when a consolidation management model is applied
> constantly in a cloud. Also, if you want to know about our virtual machines
> balancing experiments, do not hesitate to contact us!
>
>
> Thanks for your time!
> Lucas
>
> On Fri, Mar 10, 2017 at 2:03 PM, Gabriel Beims Bräscher <
> gabrasc...@gmail.com> wrote:
>
>> Dear Apache CloudStack community,
>>
>>
>> Without wishing to take the liberty, I would like to ask a bit of your
>> precious time to answer a survey. This survey will help us to provide an
>> autonomic cloud for you.
>>
>> Autonomiccs is a Brazilian Startup committed to build solutions that
>> autonomically manage and optimize cloud computing infrastructures created
>> with Apache CloudStack. Some of you may have seen a bit of our work at
>> ApacheCon Europe 2016. We hope to work alongside the Apache CloudStack
>> community, leveraging Apache CloudStack to the next level on cloud
>> computing orchestration.
>>
>> We are working hard to understand the needs of CloudStack users. This
>> survey can help us to provide Apache CloudStack users with the cloud they
>> need, delivering a competitive advantage for the Apache CloudStack
>> ecosystem.
>>
>> If all goes right, we will present the collected data at the CloudStack
>> Collaboration Conference in Miami, within the “*Building an Autonomic
>> CloudStack*” presentation.
>>
>>
>> Survey link:
>> https://docs.google.com/forms/d/e/1FAIpQLSfBhG1KNo_N_nwOBt_1
>> 8GbHK56_DTch1aEMkv4wAJnTDpE2ow/viewform
>>
>>
>> Thanks in advance for your time,
>>
>> Gabriel.
>>
>
>

RE: [VOTE] Retirement of midonet plugin

2017-03-28 Thread Marty Godsey 
+1 to retire.

Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC

-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] 
Sent: Tuesday, March 28, 2017 4:46 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: [VOTE] Retirement of midonet plugin

Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some talk, 
we converged in a retirement process and it seems that we all agree that the 
Midonet plugin should be retired. So, to formalize things, we should vote 
Midonet retirement.

All users and devs are welcome to vote here:
[+1] I *do want to retire *the Midonet plugin [0] Whatever happens I am happy 
[-1] I *do not want to retire* the Midonet plugin


[*] http://markmail.org/message/x6p3gnvqbbxcj6gs

--
Rafael Weingärtner

Re: [VOTE] Retirement of midonet plugin

2017-03-28 Thread Rubens Malheiro 
+1

Sent from my iPhone

> On 28 Mar 2017, at 17:55, Sergey Levitskiy  
> wrote:
> 
> +1
>

Re: [VOTE] Retirement of midonet plugin

2017-03-28 Thread Sergey Levitskiy 
+1

[VOTE] Retirement of midonet plugin

2017-03-28 Thread Rafael Weingärtner 
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to formalize things, we
should vote Midonet retirement.

All users and devs are welcome to vote here:
[+1] I *do want to retire *the Midonet plugin
[0] Whatever happens I am happy
[-1] I *do not want to retire* the Midonet plugin


[*] http://markmail.org/message/x6p3gnvqbbxcj6gs

--
Rafael Weingärtner

Re: Can it happen that XenServer shuts down a VM autonomously?

2017-03-28 Thread Dag Sonstebo 
Hi Melanie,

Have you ruled out that the VM might have been shut down from within the VM 
guest OS itself? 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 28/03/2017, 14:48, "Melanie Desaive"  wrote:

Hi all,

on Sunday we had an issue, because one VM was unexpetedly down. After
starting the VM in ACS everything worked fine again.

After investigating I found out the following situation:

The ACS Logs point out, that ACS received a poweroff report while the VM
was expected to be running:

---
2017-03-26 13:03:38,468 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgentCronJob-260:ctx-905a294a) VM i-86-1412-VM is at Running and
we received a power-off report while there is no pending jobs on it
2017-03-26 13:03:38,470 DEBUG [c.c.a.t.Request]
(DirectAgentCronJob-260:ctx-905a294a) Seq 28-7473723581621346009:
Sending { Cmd , MgmtId: 57177340185274, via: 28(acs-compute-6), Ver: v1,
Flags: 100011,

[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"checkBeforeCleanup":true,"vmName":"i-86-1412-VM","executeInSequence":false,"wait":0}}]
}
2017-03-26 13:03:38,470 DEBUG [c.c.a.t.Request]
(DirectAgentCronJob-260:ctx-905a294a) Seq 28-7473723581621346009:
Executing: { Cmd , MgmtId: 57177340185274, via: 28(acs-compute-6), Ver:
v1, Flags: 100011,

[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"checkBeforeCleanup":true,"vmName":"i-86-1412-VM","executeInSequence":false,"wait":0}}]
}
2017-03-26 13:03:38,480 DEBUG [c.c.h.x.r.w.x.CitrixStopCommandWrapper]
(DirectAgent-291:ctx-9b1e2233) 9. The VM i-86-1412-VM is in Stopping state
---

The xensource Log on the Compute node indicates, that the machine was
stopped:

---
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|1|events|xenops] Received an event on managed VM
e3bad3f3-c49f-873d-943f-bc8a2af365e0
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|1|queue|xenops] Queue.push ["VM_check_state",
"e3bad3f3-c49f-873d-943f-bc8a2af365e0"] onto
e3bad3f3-c49f-873d-943f-bc8a2af365e0:[  ]
Mar 26 13:00:10 acs-compute-6 xenopsd: [debug|acs-compute-6|10||xenops]
Queue.pop returned ["VM_check_state",
"e3bad3f3-c49f-873d-943f-bc8a2af365e0"]
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|10|events|xenops] Task 449410 reference events:
["VM_check_state", "e3bad3f3-c49f-873d-943f-bc8a2af365e0"]
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|2|xenstore|xenstore_watch] xenstore unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenstored:  A820862  unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenstored:  A820862  unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|10|events|xenops] VM.shutdown
e3bad3f3-c49f-873d-943f-bc8a2af365e0
---

Unfortunately I am not able to explain, how the VM.shutdown was
triggered on XenServer side. Are there known situations, when a
XenServer does trigger a VM shutdown autonomously?

Greetings,

Melanie
-- 
--

Heinlein Support GmbH
Linux: Akademie - Support - Hosting

http://www.heinlein-support.de
Tel: 030 / 40 50 51 - 0
Fax: 030 / 40 50 51 - 19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein  -- Sitz: Berlin




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Cloudstack project prospect

2017-03-28 Thread Engelmann Florian 
Dear Cloudstack list,

We do use Cloudstack in production since 2014. There have been many things 
causing trouble and many things going well. We are still running 4.5 as our 
upgrade to 4.8 was stopped by some bug. We are testing 4.9.2 right now and we 
might wait for 4.10 as we are planning to switch from Xenserver to KVM and 
would like to have VM snapshots working with KVM.

Is there any release note or roadmap reflecting what's new with 4.10? The 
official release note page is still wip I guess?

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/about.html

Looks like this is some copy clone from:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.9.2.0/about.html

As far as I red on github one important feature included is "KVM VM snapshots" 
(also with ceph blockstorage?). What are the other milestones?

Thank you very much and alle the best,
Florian


EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

T  +41 44 466 60 00
F  +41 44 466 60 10

florian.engelm...@everyware.ch
www.everyware.ch


smime.p7s
Description: S/MIME cryptographic signature

Can it happen that XenServer shuts down a VM autonomously?

2017-03-28 Thread Melanie Desaive 
Hi all,

on Sunday we had an issue, because one VM was unexpetedly down. After
starting the VM in ACS everything worked fine again.

After investigating I found out the following situation:

The ACS Logs point out, that ACS received a poweroff report while the VM
was expected to be running:

---
2017-03-26 13:03:38,468 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgentCronJob-260:ctx-905a294a) VM i-86-1412-VM is at Running and
we received a power-off report while there is no pending jobs on it
2017-03-26 13:03:38,470 DEBUG [c.c.a.t.Request]
(DirectAgentCronJob-260:ctx-905a294a) Seq 28-7473723581621346009:
Sending { Cmd , MgmtId: 57177340185274, via: 28(acs-compute-6), Ver: v1,
Flags: 100011,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"checkBeforeCleanup":true,"vmName":"i-86-1412-VM","executeInSequence":false,"wait":0}}]
}
2017-03-26 13:03:38,470 DEBUG [c.c.a.t.Request]
(DirectAgentCronJob-260:ctx-905a294a) Seq 28-7473723581621346009:
Executing: { Cmd , MgmtId: 57177340185274, via: 28(acs-compute-6), Ver:
v1, Flags: 100011,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"checkBeforeCleanup":true,"vmName":"i-86-1412-VM","executeInSequence":false,"wait":0}}]
}
2017-03-26 13:03:38,480 DEBUG [c.c.h.x.r.w.x.CitrixStopCommandWrapper]
(DirectAgent-291:ctx-9b1e2233) 9. The VM i-86-1412-VM is in Stopping state
---

The xensource Log on the Compute node indicates, that the machine was
stopped:

---
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|1|events|xenops] Received an event on managed VM
e3bad3f3-c49f-873d-943f-bc8a2af365e0
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|1|queue|xenops] Queue.push ["VM_check_state",
"e3bad3f3-c49f-873d-943f-bc8a2af365e0"] onto
e3bad3f3-c49f-873d-943f-bc8a2af365e0:[  ]
Mar 26 13:00:10 acs-compute-6 xenopsd: [debug|acs-compute-6|10||xenops]
Queue.pop returned ["VM_check_state",
"e3bad3f3-c49f-873d-943f-bc8a2af365e0"]
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|10|events|xenops] Task 449410 reference events:
["VM_check_state", "e3bad3f3-c49f-873d-943f-bc8a2af365e0"]
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|2|xenstore|xenstore_watch] xenstore unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenstored:  A820862  unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenstored:  A820862  unwatch
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
/vm/e3bad3f3-c49f-873d-943f-bc8a2af365e0/rtc/timeoffset
Mar 26 13:00:10 acs-compute-6 xenopsd:
[debug|acs-compute-6|10|events|xenops] VM.shutdown
e3bad3f3-c49f-873d-943f-bc8a2af365e0
---

Unfortunately I am not able to explain, how the VM.shutdown was
triggered on XenServer side. Are there known situations, when a
XenServer does trigger a VM shutdown autonomously?

Greetings,

Melanie
-- 
--

Heinlein Support GmbH
Linux: Akademie - Support - Hosting

http://www.heinlein-support.de
Tel: 030 / 40 50 51 - 0
Fax: 030 / 40 50 51 - 19

Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein  -- Sitz: Berlin



signature.asc
Description: OpenPGP digital signature