cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Haijiao <18602198...@163.com>
Subject Re:Re: :[VOTE] Apache Cloudstack 4.10.0.0
Date Wed, 19 Apr 2017 10:43:57 GMT
Awesome !    Feel 4.10 will be another great release.   And we will consider to upgrade  to 4.10 directly from 4.7.1.


Thanks!


在2017年04月19 18时39分, "Rajani Karuturi"<rajani@apache.org>写道:



Yes. will do over the weekend.




~ Rajani

http://cloudplatform.accelerite.com/


On April 19, 2017 at 4:07 PM, Haijiao (18602198181@163.com) wrote:

Can we merge the rest of PRs already have 2 LGTMs while community is still dealing with these blokcers ?










在2017年04月19 13时55分, "Rajani Karuturi"<rajani@apache.org>写道:


A quick update one RC2:

There are the current list of blocker.
CLOUDSTACK-9878 - Remote Access VPN that losing connection when new network
configs are introduced
CLOUDSTACK-9868 - internal LB for VPC tier is broken
CLOUDSTACK-9408 - remove runtime references to http://download.cloud.com

Thanks,

~Rajani
http://cloudplatform.accelerite.com/

On Thu, Apr 6, 2017 at 10:53 AM, Rajani Karuturi <rajani@apache.org> wrote:

> A quick update on RC2:
>
> These are the current list of blockers.
> https://github.com/apache/cloudstack/pull/2022
> https://github.com/apache/cloudstack/pull/2025
> https://issues.apache.org/jira/browse/CLOUDSTACK-9849
> https://github.com/apache/cloudstack/pull/1582
>
> I am planning to close all the PRs by weekend. The blockers which Mike
> reported is still open and needs a fix.
> If everything is resolved, we can plan for RC2 on Monday.
>
>
> ~Rajani
> http://cloudplatform.accelerite.com/
>
> On Thu, Apr 6, 2017 at 10:50 AM, Rajani Karuturi <rajani@apache.org>
> wrote:
>
>> Thanks for updating RN. Release notes is something which we haven't
>> looked at till now.
>> Any update on the xen 7.1 PR?
>>
>> ~Rajani
>> http://cloudplatform.accelerite.com/
>>
>> On Mon, Apr 3, 2017 at 6:41 PM, Pierre-Luc Dion <pdion@cloudops.com>
>> wrote:
>>
>>> Look like we need a new systemvm named "systemvm-xenserver-4.10". t also
>>> seams that older VR ex: 4.7.x are still usable if the globalsetting
>>> "minreq.sysvmtemplate.version" is changed after the first boot of
>>> cloudstack-management that upgraded the database. I'll update the release
>>> note acordingly...
>>>
>>> So this 4.10 is looking promising! :-)
>>>
>>>
>>>
>>>
>>> On Apr 1, 2017 16:02, "Pierre-Luc Dion" <pdion@cloudops.com> wrote:
>>>
>>> I'm testing upgrade to 4.10 from latest master. I have the following
>>> error
>>> when upgrading from 4.7.2 in management-server.log:
>>>
>>> 2017-04-01 15:58:12,558 DEBUG [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) Updating System Vm template IDs
>>> 2017-04-01 15:58:12,561 DEBUG [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) Updating KVM System Vms
>>> 2017-04-01 15:58:12,561 WARN [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) 4.10.0.0KVM SystemVm template not
>>> found. KVM hypervisor is not used, so not failing upgrade
>>> 2017-04-01 15:58:12,562 DEBUG [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) Updating VMware System Vms
>>> 2017-04-01 15:58:12,563 WARN [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) 4.10.0.0VMware SystemVm template
>>> not
>>> found. VMware hypervisor is not used, so not failing upgrade
>>> 2017-04-01 15:58:12,563 DEBUG [c.c.u.d.Upgrade4920to41000]
>>> (localhost-startStop-1:null) (logid:) Updating XenServer System Vms
>>> 2017-04-01 15:58:12,565 ERROR [c.c.u.DatabaseUpgradeChecker]
>>> (localhost-startStop-1:null) (logid:) Unable to upgrade the database
>>> com.cloud.utils.exception.CloudRuntimeException: 4.10.0.0XenServer
>>> SystemVm
>>> template not found. Cannot upgrade system Vms
>>> at com.cloud.upgrade.dao.Upgrade4920to41000.updateSystemVmTempl
>>> ates(Upgrade4920to41000.java:195)
>>> at com.cloud.upgrade.dao.Upgrade4920to41000.performDataMigratio
>>> n(Upgrade4920to41000.java:64)
>>> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpg
>>> radeChecker.java:426)
>>> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgra
>>> deChecker.java:507)
>>> at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif
>>> eCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65)
>>> at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif
>>> eCycle.start(CloudStackExtendedLifeCycle.java:55)
>>> at org.springframework.context.support.DefaultLifecycleProcesso
>>> r.doStart(DefaultLifecycleProcessor.java:173)
>>> at org.springframework.context.support.DefaultLifecycleProcesso
>>> r.access$200(DefaultLifecycleProcessor.java:51)
>>> at org.springframework.context.support.DefaultLifecycleProcesso
>>> r$LifecycleGroup.start(DefaultLifecycleProcessor.java:346)
>>> at org.springframework.context.support.DefaultLifecycleProcesso
>>> r.startBeans(DefaultLifecycleProcessor.java:149)
>>> at org.springframework.context.support.DefaultLifecycleProcesso
>>> r.onRefresh(DefaultLifecycleProcessor.java:112)
>>> at org.springframework.context.support.AbstractApplicationConte
>>> xt.finishRefresh(AbstractApplicationContext.java:879)
>>> at org.springframework.context.support.AbstractApplicationConte
>>> xt.refresh(AbstractApplicationContext.java:545)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
>>> at org.apache.cloudstack.spring.module.model.impl.DefaultModule
>>> DefinitionSet.load(DefaultModuleDefinitionSet.java:79)
>>> at org.apache.cloudstack.spring.module.factory.ModuleBasedConte
>>> xtFactory.loadModules(ModuleBasedContextFactory.java:37)
>>> at org.apache.cloudstack.spring.module.factory.CloudStackSpring
>>> Context.init(CloudStackSpringContext.java:71)
>>> at org.apache.cloudstack.spring.module.factory.CloudStackSpring
>>> Context.<init>(CloudStackSpringContext.java:58)
>>> at org.apache.cloudstack.spring.module.factory.CloudStackSpring
>>> Context.<init>(CloudStackSpringContext.java:62)
>>> at org.apache.cloudstack.spring.module.web.CloudStackContextLoa
>>> derListener.
>>> contextInitialized(CloudStackContextLoaderListener.java:52)
>>> at org.apache.catalina.core.StandardContext.listenerStart(Stand
>>> ardContext.java:5068)
>>> at org.apache.catalina.core.StandardContext.startInternal(Stand
>>> ardContext.java:5584)
>>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
>>> at org.apache.catalina.core.ContainerBase.addChildInternal(Cont
>>> ainerBase.java:899)
>>> at org.apache.catalina.core.ContainerBase.addChild(ContainerBas
>>> e.java:875)
>>> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
>>> at org.apache.catalina.startup.HostConfig.deployDirectory(HostC
>>> onfig.java:1260)
>>> at org.apache.catalina.startup.HostConfig$DeployDirectory.run(
>>> HostConfig.java:2002)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
>>> s.java:511)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>>
>>> Is it now mendatory to upgrade systemvm-template for this upgrade? how
>>> does
>>> the template should be named because I've tried with template
>>> name systemvm-xenserver-4.10.0.0 and systemvm-xenserver-4.10.0 and not
>>> success to start the management server :-S
>>>
>>> Thanks!
>>>
>>>
>>>
>>> *Pierre-Luc DION*
>>> Architecte de Solution Cloud | Cloud Solutions Architect
>>> t 855.652.5683
>>>
>>> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
>>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>>> w cloudops.com *|* tw @CloudOps_
>>>
>>> On Sat, Apr 1, 2017 at 3:02 PM, Tutkowski, Mike <
>>> Mike.Tutkowski@netapp.com>
>>> wrote:
>>>
>>> > I have this on my to-do list. It might take me a while, though. At the
>>> > time being, I’m busy with a customer project that is making use of the
>>> two
>>> > CloudStack environments that I have in my lab. Then, toward the end of
>>> next
>>> > week, I’m heading to Europe for about 10 days or so (customer meetings
>>> and
>>> > to present at the CloudStack Meetup in Prague hosted by Interoute).
>>> >
>>> > On 3/30/17, 4:28 AM, "Daan Hoogland" <daan.hoogland@shapeblue.com>
>>> wrote:
>>> >
>>> > Mike, can you confirm that this is not also an issue in 4.9?
>>> >
>>> > On 30/03/17 08:21, "Tutkowski, Mike" <Mike.Tutkowski@netapp.com>
>>> > wrote:
>>> >
>>> > This one may be a blocker (it’s currently marked as such):
>>> >
>>> > https://issues.apache.org/jira/browse/CLOUDSTACK-9849
>>> >
>>> > It would be nice if one of our VMware gurus could take a look
>>> at
>>> > it and see what’s going on there.
>>> >
>>> > The gist is you can’t live migrate a VM from one cluster to
>>> > another in the same datacenter (using either NFS or iSCSI as shared
>>> > storage) (which I think you should be able to do with VMware in
>>> CloudStack).
>>> >
>>> > On 3/30/17, 12:06 AM, "Haijiao" <18602198181@163.com> wrote:
>>> >
>>> > Seems only one blocker left. Are we close to release the
>>> RC2
>>> > ?
>>> >
>>> >
>>> > CLOUDSTACK-9408 - remove runtime references to
>>> > http://download.cloud.com - Daan Hoogland - Daan Hoogland
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > 在2017年03月14 00时34分, "Rajani Karuturi"<rajani@apache.org>写道
>>> :
>>> >
>>> > We still have below three blockers open. I will create RC
>>> once
>>> > they are fixed.
>>> >
>>> > ~ Rajani
>>> >
>>> > http://cloudplatform.accelerite.com/
>>> >
>>> > On March 9, 2017 at 10:09 AM, Rajani Karuturi (
>>> > rajani@apache.org)
>>> > wrote:
>>> >
>>> > We currently have the below list of blockers:
>>> >
>>> > BUGID - Summary - Assignee - Creator
>>> >
>>> > CLOUDSTACK-9827 - Storage tags stored in multiple places -
>>> > Nicolas Vazquez - Mike Tutkowski - PR Ready
>>> >
>>> > CLOUDSTACK-9811 - VR will not start, looking to configure
>>> eth3
>>> > while no such device exists on the VR. On KVM-CentOS6.8
>>> > physical
>>> > host - Unassigned - Boris Stoyanov
>>> >
>>> > CLOUDSTACK-9408 - remove runtime references to
>>> > http://download.cloud.com - Daan Hoogland - Daan Hoogland
>>> >
>>> > Can someone take a look at CLOUDSTACK-9811?
>>> >
>>> > ~ Rajani
>>> >
>>> > http://cloudplatform.accelerite.com/
>>> >
>>> > On March 9, 2017 at 3:16 AM, Tutkowski, Mike
>>> > (Mike.Tutkowski@netapp.com) wrote:
>>> >
>>> > Hi,
>>> >
>>> > Sure, I can pull that code and test.
>>> >
>>> > I might have to wait until tomorrow, though, because I’m
>>> in the
>>> > middle of trying to reproduce CLOUDSTACK-9823. Once that is
>>> > done,
>>> > I can move on to your PR.
>>> >
>>> > Thanks!
>>> > Mike
>>> >
>>> > On 3/8/17, 1:45 PM, "Nicolas Vazquez" <
>>> nicovazquez90@gmail.com
>>> > >
>>> > wrote:
>>> >
>>> > Hi Mike,
>>> >
>>> > Thanks for reporting this issue! We've been working on it
>>> and
>>> > created this
>>> > PR: https://github.com/apache/cloudstack/pull/1994. We've
>>> been
>>> > testing it
>>> > and seems to be solving the issues reported, can you please
>>> > repeat your
>>> > tests on it?
>>> >
>>> > Thanks,
>>> > Nicolas
>>> >
>>> > 2017-03-07 21:52 GMT-03:00 Tutkowski, Mike
>>> > <Mike.Tutkowski@netapp.com>:
>>> >
>>> > > Here’s the ticket:
>>> > >
>>> > > https://issues.apache.org/jira/browse/CLOUDSTACK-9827
>>> > >
>>> > > On 3/7/17, 1:51 PM, "Tutkowski, Mike"
>>> > <Mike.Tutkowski@netapp.com> wrote:
>>> > >
>>> > > Yes, I can open a ticket.
>>> > >
>>> > > > On Mar 7, 2017, at 1:50 PM, Sergey Levitskiy <
>>> > > Sergey.Levitskiy@autodesk.com> wrote:
>>> > > >
>>> > > > Yes that’s the bug. Can you open a ticket for this? @
>>> > nvazquez can
>>> > > you take a look?
>>> > > >
>>> > > > On 3/7/17, 12:44 PM, "Tutkowski, Mike"
>>> > <Mike.Tutkowski@netapp.com>
>>> > > wrote:
>>> > > >
>>> > > > This does seem messed up.
>>> > > >
>>> > > > If I add a new primary storage and give it a storage
>>> tag,
>>> > the tag
>>> > > ends up in storage_pool_details.
>>> > > >
>>> > > > If I edit an existing storage pool’s storage tags, it
>>> > places
>>> > them
>>> > > in storage_pool_tags.
>>> > > >
>>> > > > On 3/7/17, 1:39 PM, "Tutkowski, Mike"
>>> > <Mike.Tutkowski@netapp.com>
>>> > > wrote:
>>> > > >
>>> > > > I believe I have found another bug (one that we should
>>> > either
>>> > > fix or examine in detail before releasing 4.10).
>>> > > >
>>> > > > It looks like we have a new table:
>>> cloud.storage_pool_tags.
>>> > > >
>>> > > > The addition of this table seems to have broken the
>>> > > listStorageTags API command. When this command runs, it
>>> > doesn’t pick up any
>>> > > storage tags for me (and I know I have one storage tag).
>>> > > >
>>> > > > This data used to be stored in the
>>> > cloud.storage_pool_details
>>> > > table. It’s good to put it in its own table, but will our
>>> > upgrade process
>>> > > move the existing tags from storage_pool_details to
>>> > storage_pool_tags?
>>> > > >
>>> > > > I have not yet opened a ticket for this. I want to
>>> examine
>>> > it
>>> > > a bit more before doing so.
>>> > > >
>>> > > > On 3/7/17, 8:10 AM, "Tutkowski, Mike" <
>>> > > Mike.Tutkowski@netapp.com> wrote:
>>> > > >
>>> > > > No VM snapshot.
>>> > > >
>>> > > > I tried while the VM was in the Running state and then
>>> I
>>> > > also tried in the Stopped state. Same results.
>>> > > >
>>> > > >> On Mar 7, 2017, at 7:54 AM, Sergey Levitskiy <
>>> > > Sergey.Levitskiy@autodesk.com> wrote:
>>> > > >>
>>> > > >> Is VM has an VMsnaphsot? Is VM in Stopped state?
>>> > > >>
>>> > > >> On 3/6/17, 10:32 PM, "Tutkowski, Mike"
>>> > <Mike.Tutkowski@netapp.com>
>>> > > wrote:
>>> > > >>
>>> > > >> I seem to have found another blocker:
>>> > > >>
>>> > > >> https://issues.apache.org/jira/browse/CLOUDSTACK-9822
>>> > > >>
>>> > > >> On 3/6/17, 9:51 PM, "Rajani Karuturi" <
>>> rajani@apache.org>
>>> > wrote:
>>> > > >>
>>> > > >> PRs are ready for the blockers. Waiting for reviews
>>> and
>>> > test
>>> > > >> results. Once they are ready, I will merge them(and a
>>> few
>>> > more
>>> > > >> bug fixes) and create RC2 (probably tomorrow,
>>> Wednesday)
>>> > > >>
>>> > > >> Thanks,
>>> > > >>
>>> > > >> ~ Rajani
>>> > > >>
>>> > > >> http://cloudplatform.accelerite.com/
>>> > > >>
>>> > > >> On March 3, 2017 at 4:30 PM, Rajani Karuturi (
>>> > > rajani@apache.org)
>>> > > >> wrote:
>>> > > >>
>>> > > >> I will create RC2 on Monday with the fixes mentioned
>>> in my
>>> > > >> previous mail.
>>> > > >>
>>> > > >> ~ Rajani
>>> > > >>
>>> > > >> http://cloudplatform.accelerite.com/
>>> > > >>
>>> > > >> On March 3, 2017 at 2:36 PM, Rohit Yadav
>>> > > >> (rohit.yadav@shapeblue.com) wrote:
>>> > > >>
>>> > > >> Thanks Koushik, I did not realize Kishan had sent this
>>> > > already.
>>> > > >> Let's get either of the PRs merged and kick a RC2.
>>> > > >>
>>> > > >> Regards.
>>> > > >>
>>> > > >> ________________________________
>>> > > >> From: Koushik Das <koushik.das@accelerite.com>
>>> > > >> Sent: 03 March 2017 14:14:56
>>> > > >> To: dev@cloudstack.apache.org
>>> > > >> Subject: Re: :[VOTE] Apache Cloudstack 4.10.0.0
>>> > > >>
>>> > > >> Looks like there is already a PR for the same issue
>>> > > >> https://github.com/apache/cloudstack/pull/1982 from
>>> > Kishan.
>>> > > >>
>>> > > >> -Koushik
>>> > > >>
>>> > > >> On 03/03/17, 1:58 PM, "Rohit Yadav" <
>>> > > rohit.yadav@shapeblue.com>
>>> > > >> wrote:
>>> > > >>
>>> > > >> -1 (binding)
>>> > > >>
>>> > > >> All, I've found an upgrade blocker. Pre 4.6 users are
>>> > required
>>> > > >> to seed 4.6 systemvmtemplate to proceed with the
>>> upgrade
>>> > > >> otherwise upgrade fails, and from 4.9 upgrade to 4.10
>>> does
>>> > no
>>> > > >> check/enforcement that 4.10 based systemvmtemplate has
>>> > been
>>> > > >> seeded/registered, nor the minimum required
>>> > systemvmtemplate
>>> > > >> version is changed from 4.6.0 to 4.10.0.
>>> > > >>
>>> > > >> After we have merged the strongswan/java8 PR, I had
>>> > updated
>>> > > the
>>> > > >> upgrade docs on how to upgrade the systemvmtemplate
>>> here:
>>> > > >>
>>> > > >> http://docs.cloudstack.apache.
>>> org/projects/cloudstack-
>>> > > release-notes/en/4.10/upgrade/upgrade-4.9.html
>>> > > >>
>>> > > >> Using the above, I've tried to fix these issues here,
>>> > please
>>> > > >> review and merge for RC2:
>>> > > >>
>>> > > >> https://github.com/apache/cloudstack/pull/1983
>>> > > >>
>>> > > >> <https://github.com/apache/cloudstack/pull/1983>With
>>> > above
>>> > > fix,
>>> > > >> the aim is that users only seed the 4.10
>>> systemvmtemplate
>>> > > before
>>> > > >> upgrade and post-upgrade the upgrade paths fix the
>>> > entries,
>>> > > >> global setting etc.
>>> > > >>
>>> > > >> Regards.
>>> > > >>
>>> > > >> ________________________________
>>> > > >> From: Tutkowski, Mike <Mike.Tutkowski@netapp.com>
>>> > > >> Sent: 02 March 2017 22:39:08
>>> > > >> To: dev@cloudstack.apache.org
>>> > > >> Subject: Re: :[VOTE] Apache Cloudstack 4.10.0.0
>>> > > >>
>>> > > >> I rolled back to my master branch at
>>> > > >> da66b06e7d562393da2e4b52206943f8bad49d10 and it
>>> works.
>>> > > >>
>>> > > >> It appears something that went into after that commit
>>> has
>>> > > broken
>>> > > >> this. It looks like this SHA is about two weeks old
>>> and
>>> > that
>>> > > 43
>>> > > >> commits have gone into master since it.
>>> > > >>
>>> > > >> On 3/2/17, 7:06 AM, "Tutkowski, Mike"
>>> > > >> <Mike.Tutkowski@netapp.com> wrote:
>>> > > >>
>>> > > >> According to where the code fails, though, it appears
>>> to
>>> > be
>>> > a
>>> > > >> networking problem. If I set a breakpoint before the
>>> > failure
>>> > > and
>>> > > >> change a variable to say that security groups are not
>>> > being
>>> > > used,
>>> > > >> then the VM starts.
>>> > > >>
>>> > > >> I think this is a recently introduced problem because
>>> I
>>> > have
>>> > > >> another branch based off of a slightly older version
>>> of
>>> > master
>>> > > >> and it works fine here.
>>> > > >>
>>> > > >>> On Mar 2, 2017, at 6:51 AM, Pierre-Luc Dion
>>> > > >> <pdion@cloudops.com> wrote:
>>> > > >>>
>>> > > >>> Hi Mike,
>>> > > >>> Try vm with at least 512MB for memory.
>>> > > >>>
>>> > > >>>> On Mar 1, 2017 15:01, "Tutkowski, Mike"
>>> > > >> <Mike.Tutkowski@netapp.com> wrote:
>>> > > >>>>
>>> > > >>>> I see the following exception when trying to deploy
>>> a
>>> > user VM
>>> > > >> in a Basic
>>> > > >>>> Zone with two XenServer 6.5 hosts in one cluster. My
>>> > system
>>> > > >> VMs have all
>>> > > >>>> deployed properly. The user template gets downloaded
>>> > fine. I
>>> > > >> can see the
>>> > > >>>> user VM begin to start on a XenServer host, then it
>>> goes
>>> > > >> away. We then
>>> > > >>>> automatically try on the other host. I can see the
>>> VM
>>> > begin
>>> > > >> to start there
>>> > > >>>> for a moment, then it goes away.
>>> > > >>>>
>>> > > >>>> I am just deploying the user VM’s template and root
>>> disk
>>> > to
>>> > > >> NFS (same
>>> > > >>>> place where the template and root disks of my
>>> system VMs
>>> > > >> are).
>>> > > >>>>
>>> > > >>>> I am using the built-in XenServer CentOS 5.6 (64
>>> bit)
>>> > > >> template with 1
>>> > > >>>> vCPU, 500 MHz, and 256 MB memory.
>>> > > >>>>
>>> > > >>>> WARN [c.c.a.r.v.VirtualRoutingResource]
>>> > > >> (DirectAgent-7:ctx-35aded78)
>>> > > >>>> (logid:aab9c320) Expected 1 answers while executing
>>> > > >> VmDataCommand but
>>> > > >>>> received 2
>>> > > >>>> WARN [c.c.v.VirtualMachinePowerStateSyncImpl]
>>> > > >> (DirectAgentCronJob-14:ctx-27fb1ac3)
>>> > > >>>> (logid:2c342f23) VM state was updated but update
>>> time is
>>> > > >> null?! vm id: 6
>>> > > >>>> INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
>>> > > >> (AsyncJobMgr-Heartbeat-1:ctx-2c7d2dce)
>>> > > >>>> (logid:a56a9a8c) Begin cleanup expired async-jobs
>>> > > >>>> INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
>>> > > >> (AsyncJobMgr-Heartbeat-1:ctx-2c7d2dce)
>>> > > >>>> (logid:a56a9a8c) End cleanup expired async-jobs
>>> > > >>>> INFO [c.c.u.AccountManagerImpl]
>>> > > >> (AccountChecker-1:ctx-383a632c)
>>> > > >>>> (logid:541e9ba5) Found 0 removed accounts to cleanup
>>> > > >>>> INFO [c.c.u.AccountManagerImpl]
>>> > > >> (AccountChecker-1:ctx-383a632c)
>>> > > >>>> (logid:541e9ba5) Found 0 disabled accounts to
>>> cleanup
>>> > > >>>> INFO [c.c.u.AccountManagerImpl]
>>> > > >> (AccountChecker-1:ctx-383a632c)
>>> > > >>>> (logid:541e9ba5) Found 0 inactive domains to cleanup
>>> > > >>>> INFO [c.c.u.AccountManagerImpl]
>>> > > >> (AccountChecker-1:ctx-383a632c)
>>> > > >>>> (logid:541e9ba5) Found 0 disabled projects to
>>> cleanup
>>> > > >>>> WARN [c.c.h.x.r.CitrixResourceBase]
>>> > > >> (DirectAgent-16:ctx-7c901443)
>>> > > >>>> (logid:aab9c320) callHostPlugin failed for cmd:
>>> > > >> default_network_rules with
>>> > > >>>> args secIps: 0:, vmName: i-2-6-VM, vmID: 6, vmIP:
>>> > > >> 10.117.40.53, vmMAC:
>>> > > >>>> 06:b2:f4:00:00:22, due to There was a failure
>>> > communicating
>>> > > >> with the
>>> > > >>>> plugin.
>>> > > >>>> WARN [c.c.h.x.r.w.x.CitrixStartCommandWrapper]
>>> > > >>>> (DirectAgent-16:ctx-7c901443) (logid:aab9c320) Catch
>>> > > >> Exception: class
>>> > > >>>> com.cloud.utils.exception.CloudRuntimeException
>>> due to
>>> > > >>>> com.cloud.utils.exception.CloudRuntimeException:
>>> > > >> callHostPlugin failed
>>> > > >>>> for cmd: default_network_rules with args secIps: 0:,
>>> > vmName:
>>> > > >> i-2-6-VM,
>>> > > >>>> vmID: 6, vmIP: 10.117.40.53, vmMAC:
>>> 06:b2:f4:00:00:22,
>>> > due to
>>> > > >> There was a
>>> > > >>>> failure communicating with the plugin.
>>> > > >>>> com.cloud.utils.exception.CloudRuntimeException:
>>> > > >> callHostPlugin failed
>>> > > >>>> for cmd: default_network_rules with args secIps: 0:,
>>> > vmName:
>>> > > >> i-2-6-VM,
>>> > > >>>> vmID: 6, vmIP: 10.117.40.53, vmMAC:
>>> 06:b2:f4:00:00:22,
>>> > due to
>>> > > >> There was a
>>> > > >>>> failure communicating with the plugin.
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> callHostPlugin(CitrixResourceBase.java:338)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:188)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:53)
>>> > > >>>> at com.cloud.hypervisor.xenserver.resource.wrapper.
>>> > > >>>>
>>> > > >> xenbase.CitrixRequestWrapper.e
>>> > xecute(CitrixRequestWrapper.
>>> > > java:122)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> executeRequest(CitrixResourceBase.java:1691)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.agent.manager.Direc
>>> tAgentAttache$Task.runInContext(
>>> > > >>>> DirectAgentAttache.java:315)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > > >> ScheduledFutureTask.access$201
>>> > (ScheduledThreadPoolExecutor.
>>> > > java:180)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > ScheduledFutureTask.run(Sched
>>> uledThreadPoolExecutor.java:293)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> WARN [c.c.h.x.r.CitrixResourceBase]
>>> > > >> (DirectAgent-16:ctx-7c901443)
>>> > > >>>> (logid:aab9c320) Unable to start i-2-6-VM due to
>>> > > >>>> com.cloud.utils.exception.CloudRuntimeException:
>>> > > >> callHostPlugin failed
>>> > > >>>> for cmd: default_network_rules with args secIps: 0:,
>>> > vmName:
>>> > > >> i-2-6-VM,
>>> > > >>>> vmID: 6, vmIP: 10.117.40.53, vmMAC:
>>> 06:b2:f4:00:00:22,
>>> > due to
>>> > > >> There was a
>>> > > >>>> failure communicating with the plugin.
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> callHostPlugin(CitrixResourceBase.java:338)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:188)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:53)
>>> > > >>>> at com.cloud.hypervisor.xenserver.resource.wrapper.
>>> > > >>>>
>>> > > >> xenbase.CitrixRequestWrapper.e
>>> > xecute(CitrixRequestWrapper.
>>> > > java:122)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> executeRequest(CitrixResourceBase.java:1691)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.agent.manager.Direc
>>> tAgentAttache$Task.runInContext(
>>> > > >>>> DirectAgentAttache.java:315)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > > >> ScheduledFutureTask.access$201
>>> > (ScheduledThreadPoolExecutor.
>>> > > java:180)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > ScheduledFutureTask.run(Sched
>>> uledThreadPoolExecutor.java:293)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> INFO [o.a.c.e.o.NetworkOrchestrator]
>>> > > >> (Network-Scavenger-1:ctx-2058d5ac)
>>> > > >>>> (logid:bf8885a0) NetworkGarbageCollector uses '20'
>>> > seconds
>>> > > >> for GC interval.
>>> > > >>>> WARN [c.c.h.x.r.CitrixResourceBase]
>>> > > >> (DirectAgent-16:ctx-7c901443)
>>> > > >>>> (logid:aab9c320) Unable to clean up VBD due to
>>> > > >>>> You gave an invalid object reference. The object may
>>> > have
>>> > > >> recently been
>>> > > >>>> deleted. The class parameter gives the type of
>>> reference
>>> > > >> given, and the
>>> > > >>>> handle parameter echoes the bad value given.
>>> > > >>>> at
>>> > com.xensource.xenapi.Types.checkResponse(Types.java:693)
>>> > > >>>> at
>>> > > >>
>>> > com.xensource.xenapi.Connecti
>>> on.dispatch(Connection.java:395)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver.resource.
>>> > > XenServerConnectionPool$
>>> > > >>>>
>>> > > >> XenServerConnection.dispatch(X
>>> > enServerConnectionPool.java:
>>> > > 457)
>>> > > >>>> at com.xensource.xenapi.VBD.unplug(VBD.java:1109)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> handleVmStartFailure(CitrixResourceBase.java:3576)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:210)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:53)
>>> > > >>>> at com.cloud.hypervisor.xenserver.resource.wrapper.
>>> > > >>>>
>>> > > >> xenbase.CitrixRequestWrapper.e
>>> > xecute(CitrixRequestWrapper.
>>> > > java:122)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> executeRequest(CitrixResourceBase.java:1691)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.agent.manager.Direc
>>> tAgentAttache$Task.runInContext(
>>> > > >>>> DirectAgentAttache.java:315)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > > >> ScheduledFutureTask.access$201
>>> > (ScheduledThreadPoolExecutor.
>>> > > java:180)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > ScheduledFutureTask.run(Sched
>>> uledThreadPoolExecutor.java:293)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> WARN [c.c.h.x.r.CitrixResourceBase]
>>> > > >> (DirectAgent-16:ctx-7c901443)
>>> > > >>>> (logid:aab9c320) Unable to clean up VBD due to
>>> > > >>>> You gave an invalid object reference. The object may
>>> > have
>>> > > >> recently been
>>> > > >>>> deleted. The class parameter gives the type of
>>> reference
>>> > > >> given, and the
>>> > > >>>> handle parameter echoes the bad value given.
>>> > > >>>> at
>>> > com.xensource.xenapi.Types.checkResponse(Types.java:693)
>>> > > >>>> at
>>> > > >>
>>> > com.xensource.xenapi.Connecti
>>> on.dispatch(Connection.java:395)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver.resource.
>>> > > XenServerConnectionPool$
>>> > > >>>>
>>> > > >> XenServerConnection.dispatch(X
>>> > enServerConnectionPool.java:
>>> > > 457)
>>> > > >>>> at com.xensource.xenapi.VBD.unplug(VBD.java:1109)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> handleVmStartFailure(CitrixResourceBase.java:3576)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:210)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:53)
>>> > > >>>> at com.cloud.hypervisor.xenserver.resource.wrapper.
>>> > > >>>>
>>> > > >> xenbase.CitrixRequestWrapper.e
>>> > xecute(CitrixRequestWrapper.
>>> > > java:122)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> executeRequest(CitrixResourceBase.java:1691)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.agent.manager.Direc
>>> tAgentAttache$Task.runInContext(
>>> > > >>>> DirectAgentAttache.java:315)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > > >> ScheduledFutureTask.access$201
>>> > (ScheduledThreadPoolExecutor.
>>> > > java:180)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > ScheduledFutureTask.run(Sched
>>> uledThreadPoolExecutor.java:293)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> WARN [c.c.h.x.r.CitrixResourceBase]
>>> > > >> (DirectAgent-16:ctx-7c901443)
>>> > > >>>> (logid:aab9c320) Unable to cleanup VIF
>>> > > >>>> You gave an invalid object reference. The object may
>>> > have
>>> > > >> recently been
>>> > > >>>> deleted. The class parameter gives the type of
>>> reference
>>> > > >> given, and the
>>> > > >>>> handle parameter echoes the bad value given.
>>> > > >>>> at
>>> > com.xensource.xenapi.Types.checkResponse(Types.java:693)
>>> > > >>>> at
>>> > > >>
>>> > com.xensource.xenapi.Connecti
>>> on.dispatch(Connection.java:395)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver.resource.
>>> > > XenServerConnectionPool$
>>> > > >>>>
>>> > > >> XenServerConnection.dispatch(X
>>> > enServerConnectionPool.java:
>>> > > 457)
>>> > > >>>> at com.xensource.xenapi.VIF.unplug(VIF.java:921)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> handleVmStartFailure(CitrixResourceBase.java:3584)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:210)
>>> > > >>>> at
>>> > com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
>>> > > >>>>
>>> > > >>
>>> > CitrixStartCommandWrapper.exe
>>> cute(CitrixStartCommandWrapper.
>>> > > java:53)
>>> > > >>>> at com.cloud.hypervisor.xenserver.resource.wrapper.
>>> > > >>>>
>>> > > >> xenbase.CitrixRequestWrapper.e
>>> > xecute(CitrixRequestWrapper.
>>> > > java:122)
>>> > > >>>> at
>>> > > >> com.cloud.hypervisor.xenserver
>>> > .resource.CitrixResourceBase.
>>> > > >>>> executeRequest(CitrixResourceBase.java:1691)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.agent.manager.Direc
>>> tAgentAttache$Task.runInContext(
>>> > > >>>> DirectAgentAttache.java:315)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > > >> ScheduledFutureTask.access$201
>>> > (ScheduledThreadPoolExecutor.
>>> > > java:180)
>>> > > >>>> at java.util.concurrent.Scheduled
>>> ThreadPoolExecutor$
>>> > > >>>>
>>> > ScheduledFutureTask.run(Sched
>>> uledThreadPoolExecutor.java:293)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> INFO [c.c.v.VirtualMachineManagerImpl]
>>> > > >> (Work-Job-Executor-2:ctx-bc104380
>>> > > >>>> job-25/job-27 ctx-8c946a5b) (logid:aab9c320) Unable
>>> to
>>> > start
>>> > > >> VM on
>>> > > >>>> Host[-2-Routing] due to Unable to start i-2-6-VM
>>> due to
>>> > > >>>> ERROR [c.c.v.VmWorkJobHandlerProxy]
>>> > > >> (Work-Job-Executor-2:ctx-bc104380
>>> > > >>>> job-25/job-27 ctx-8c946a5b) (logid:aab9c320)
>>> Invocation
>>> > > >> exception, caused
>>> > > >>>> by:
>>> > com.cloud.exception.InsufficientServerCapacityException:
>>> > > >> Unable to
>>> > > >>>> create a deployment for
>>> VM[User|i-2-6-VM]Scope=interfa
>>> > ce
>>> > > >>>> com.cloud.dc.DataCenter; id=1
>>> > > >>>> INFO [c.c.v.VmWorkJobHandlerProxy]
>>> > > >> (Work-Job-Executor-2:ctx-bc104380
>>> > > >>>> job-25/job-27 ctx-8c946a5b) (logid:aab9c320) Rethrow
>>> > > >> exception
>>> > > >>>> com.cloud.exception.Insufficie
>>> > ntServerCapacityException:
>>> > > >> Unable to create
>>> > > >>>> a deployment for VM[User|i-2-6-VM]Scope=interface
>>> > > >>>> com.cloud.dc.DataCenter; id=1
>>> > > >>>> ERROR [c.c.v.VmWorkJobDispatcher]
>>> > > >> (Work-Job-Executor-2:ctx-bc104380
>>> > > >>>> job-25/job-27) (logid:aab9c320) Unable to complete
>>> > AsyncJobVO
>>> > > >> {id:27,
>>> > > >>>> userId: 2, accountId: 2, instanceType: null,
>>> instanceId:
>>> > > >> null, cmd:
>>> > > >>>> com.cloud.vm.VmWorkStart, cmdInfo:
>>> > > >> rO0ABXNyABhjb20uY2xvdWQudm0uVm
>>> > > >>>>
>>> > 1Xb3JrU3RhcnR9cMGsvxz73gIAC0o
>>> ABGRjSWRMAAZhdm9pZHN0ADBMY29tL2
>>> > > >>>>
>>> > Nsb3VkL2RlcGxveS9EZXBsb3ltZW5
>>> 0UGxhbm5lciRFeGNsdWRlTGlzdDtMAA
>>> > > >>>> ljbHVzdGVySWR0ABBMamF2YS9sYW5n
>>> L0xvbmc7TAAGaG9zdElkcQB-
>>> > > >>>>
>>> > AAJMAAtqb3VybmFsTmFtZXQAEkxqY
>>> XZhL2xhbmcvU3RyaW5nO0wAEXBoeXNp
>>> > > >>>>
>>> > > >> Y2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-
>>> > > AANMAAVwb2RJZHEAfgACTAAGcG9vbE
>>> > > >>>>
>>> > > >> lkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS
>>> > > 91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-
>>> > > >>>>
>>> > > >> AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-
>>> > > ZtlbwJWdrAgAESgAJYWNjb3VudElkS
>>> > > >>>>
>>> > > >> gAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-
>>> > > AAN4cAAAAAAAAAACAAAAAAAAAAIAAA
>>> > > >>>>
>>> > AAAAAABnQAGVZpcnR1YWxNYWNoaW5
>>> lTWFuYWdlckltcGwAAAAAAAAAAHBwcH
>>> > > >>>>
>>> > BwcHBwc3IAEWphdmEudXRpbC5IYXN
>>> oTWFwBQfawcMWYNEDAAJGAApsb2FkRm
>>> > > >>>> FjdG9ySQAJdGhyZXNob2xkeHA_QAAA
>>> > AAAADHcIAAAAEAAAAAF0AApWbV
>>> > > >>>> Bhc3N3b3JkdAAcck8wQUJYUUFEbk5o
>>> ZG1Wa1gzQmhjM04zYjNKa3hw,
>>> > > >> cmdVersion: 0,
>>> > > >>>> status: IN_PROGRESS, processStatus: 0, resultCode:
>>> 0,
>>> > result:
>>> > > >> null,
>>> > > >>>> initMsid: 52237617797, completeMsid: null,
>>> lastUpdated:
>>> > null,
>>> > > >> lastPolled:
>>> > > >>>> null, created: Wed Mar 01 12:51:32 MST 2017}, job
>>> > origin:25
>>> > > >>>> com.cloud.exception.Insufficie
>>> > ntServerCapacityException:
>>> > > >> Unable to create
>>> > > >>>> a deployment for VM[User|i-2-6-VM]Scope=interface
>>> > > >>>> com.cloud.dc.DataCenter; id=1
>>> > > >>>> at
>>> > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
>>> > > >>>> VirtualMachineManagerImpl.java:961)
>>> > > >>>> at
>>> > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
>>> > > >>>> VirtualMachineManagerImpl.java:4661)
>>> > > >>>> at sun.reflect.NativeMethodAccess
>>> orImpl.invoke0(Native
>>> > > >> Method)
>>> > > >>>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>>> > > >>>> NativeMethodAccessorImpl.java:62)
>>> > > >>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>> > > >>>> DelegatingMethodAccessorImpl.java:43)
>>> > > >>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> > > >>>> at com.cloud.vm.VmWorkJobHandlerP
>>> roxy.handleVmWorkJob(
>>> > > >>>> VmWorkJobHandlerProxy.java:107)
>>> > > >>>> at
>>> > com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(
>>> > > >>>> VirtualMachineManagerImpl.java:4822)
>>> > > >>>> at com.cloud.vm.VmWorkJobDispatcher.runJob(
>>> > > >>>> VmWorkJobDispatcher.java:102)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.framework.jobs.impl.
>>> > > AsyncJobManagerImpl$5.
>>> > > >>>> runInContext(AsyncJobManagerImpl.java:554)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at org.apache.cloudstack.framework.jobs.impl.
>>> > > >>>> AsyncJobManagerImpl$5.run(Asyn
>>> cJobManagerImpl.java:502)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> INFO [o.a.c.f.j.i.AsyncJobMonitor]
>>> > > >> (Work-Job-Executor-2:ctx-bc104380
>>> > > >>>> job-25/job-27) (logid:aab9c320) Remove job-27 from
>>> job
>>> > > >> monitoring
>>> > > >>>> WARN [o.a.c.alerts] (API-Job-Executor-1:ctx-f78720
>>> 1d
>>> > job-25
>>> > > >>>> ctx-56356c1a) (logid:aab9c320) alertType:: 8 //
>>> > > >> dataCenterId:: 1 //
>>> > > >>>> podId:: 1 // clusterId:: null // message:: Failed to
>>> > deploy
>>> > > >> Vm with Id: 6,
>>> > > >>>> on Host with Id: null
>>> > > >>>> ERROR [c.c.a.ApiAsyncJobDispatcher]
>>> > > >> (API-Job-Executor-1:ctx-f787201d
>>> > > >>>> job-25) (logid:aab9c320) Unexpected exception while
>>> > executing
>>> > > >>>>
>>> > org.apache.cloudstack.api.com
>>> mand.admin.vm.DeployVMCmdByAdmin
>>> > > >>>> com.cloud.utils.exception.CloudRuntimeException:
>>> Unable
>>> > to
>>> > > >> start a VM due
>>> > > >>>> to insufficient capacity
>>> > > >>>> at com.cloud.vm.VirtualMachineManagerImpl.start(
>>> > > >>>> VirtualMachineManagerImpl.java:623)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.engine.cloud.entity.api.
>>> > > VMEntityManagerImpl.
>>> > > >>>> deployVirtualMachine(VMEntityManagerImpl.java:242)
>>> > > >>>> at org.apache.cloudstack.engine.cloud.entity.api.
>>> > > >>>>
>>> > > >> VirtualMachineEntityImpl.deploy(
>>> > > VirtualMachineEntityImpl.java:212)
>>> > > >>>> at com.cloud.vm.UserVmManagerImpl
>>> .startVirtualMachine(
>>> > > >>>> UserVmManagerImpl.java:4084)
>>> > > >>>> at com.cloud.vm.UserVmManagerImpl
>>> .startVirtualMachine(
>>> > > >>>> UserVmManagerImpl.java:3682)
>>> > > >>>> at com.cloud.vm.UserVmManagerImpl
>>> .startVirtualMachine(
>>> > > >>>> UserVmManagerImpl.java:3670)
>>> > > >>>> at sun.reflect.NativeMethodAccess
>>> orImpl.invoke0(Native
>>> > > >> Method)
>>> > > >>>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>>> > > >>>> NativeMethodAccessorImpl.java:62)
>>> > > >>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>> > > >>>> DelegatingMethodAccessorImpl.java:43)
>>> > > >>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> > > >>>> at org.springframework.aop.support.AopUtils.
>>> > > >>>> invokeJoinpointUsingReflection(AopUtils.java:333)
>>> > > >>>> at
>>> > > >>
>>> > org.springframework.aop.frame
>>> work.ReflectiveMethodInvocation.
>>> > > >>>> invokeJoinpoint(ReflectiveMeth
>>> odInvocation.java:190)
>>> > > >>>> at
>>> > > >>
>>> > org.springframework.aop.frame
>>> work.ReflectiveMethodInvocation.
>>> > > >>>> proceed(ReflectiveMethodInvocation.java:157)
>>> > > >>>> at org.apache.cloudstack.network.
>>> contrail.management.
>>> > > >>>> EventUtils$EventInterceptor.in
>>> voke(EventUtils.java:107)
>>> > > >>>> at
>>> > > >>
>>> > org.springframework.aop.frame
>>> work.ReflectiveMethodInvocation.
>>> > > >>>> proceed(ReflectiveMethodInvocation.java:168)
>>> > > >>>> at com.cloud.event.ActionEventInterceptor.invoke(
>>> > > >>>> ActionEventInterceptor.java:51)
>>> > > >>>> at
>>> > > >>
>>> > org.springframework.aop.frame
>>> work.ReflectiveMethodInvocation.
>>> > > >>>> proceed(ReflectiveMethodInvocation.java:168)
>>> > > >>>> at
>>> > > >> org.springframework.aop.interceptor.
>>> > > ExposeInvocationInterceptor.
>>> > > >>>> invoke(ExposeInvocationInterceptor.java:92)
>>> > > >>>> at
>>> > > >>
>>> > org.springframework.aop.frame
>>> work.ReflectiveMethodInvocation.
>>> > > >>>> proceed(ReflectiveMethodInvocation.java:179)
>>> > > >>>> at org.springframework.aop.framew
>>> > ork.JdkDynamicAopProxy.
>>> > > >>>> invoke(JdkDynamicAopProxy.java:213)
>>> > > >>>> at com.sun.proxy.$Proxy186.startV
>>> irtualMachine(Unknown
>>> > > >> Source)
>>> > > >>>> at org.apache.cloudstack.api.command.admin.vm.
>>> > > >>>> DeployVMCmdByAdmin.execute(Dep
>>> loyVMCmdByAdmin.java:50)
>>> > > >>>> at
>>> > > >>
>>> > com.cloud.api.ApiDispatcher.d
>>> ispatch(ApiDispatcher.java:150)
>>> > > >>>> at com.cloud.api.ApiAsyncJobDispatcher.runJob(
>>> > > >>>> ApiAsyncJobDispatcher.java:108)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.framework.jobs.impl.
>>> > > AsyncJobManagerImpl$5.
>>> > > >>>> runInContext(AsyncJobManagerImpl.java:554)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable$1.run(
>>> > > >>>> ManagedContextRunnable.java:49)
>>> > > >>>> at org.apache.cloudstack.managed.context.impl.
>>> > > >>>>
>>> > DefaultManagedContext$1.call(
>>> DefaultManagedContext.java:56)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> callWithContext(DefaultManagedContext.java:103)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.impl.
>>> > > DefaultManagedContext.
>>> > > >>>> runWithContext(DefaultManagedContext.java:53)
>>> > > >>>> at
>>> > > >> org.apache.cloudstack.managed.context.
>>> > > ManagedContextRunnable.run(
>>> > > >>>> ManagedContextRunnable.java:46)
>>> > > >>>> at org.apache.cloudstack.framework.jobs.impl.
>>> > > >>>> AsyncJobManagerImpl$5.run(Asyn
>>> cJobManagerImpl.java:502)
>>> > > >>>> at java.util.concurrent.Executors$RunnableAdapter.
>>> > > >>>> call(Executors.java:511)
>>> > > >>>> at
>>> > java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(
>>> > > >>>> ThreadPoolExecutor.java:1142)
>>> > > >>>> at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(
>>> > > >>>> ThreadPoolExecutor.java:617)
>>> > > >>>> at java.lang.Thread.run(Thread.java:745)
>>> > > >>>> Caused by:
>>> > > >> com.cloud.exception.Insufficie
>>> ntServerCapacityException:
>>> > > >>>> Unable to create a deployment for
>>> > > >> VM[User|i-2-6-VM]Scope=interface
>>> > > >>>> com.cloud.dc.DataCenter; id=1
>>> > > >>>> at
>>> > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
>>> > > >>>> VirtualMachineManagerImpl.java:961)
>>> > > >>>> at
>>> > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
>>> > > >>>> VirtualMachineManagerImpl.java:4661)
>>> > > >>>> at sun.reflect.NativeMethodAccess
>>> orImpl.invoke0(Native
>>> > > >> Method)
>>> > > >>>> ... 18 more
>>> > > >>>>
>>> > > >>>> On 3/1/17, 8:52 AM, "Pierre-Luc Dion"
>>> > <pdion891@apache.org>
>>> > > >> wrote:
>>> > > >>>>
>>> > > >>>> Do we support centos6 with this 4.10 on jdk8?
>>> > > >>>>
>>> > > >>>> Because I did not had much success to install 4.10
>>> jdk8
>>> > on
>>> > > >> centos6
>>> > > >>>> and it
>>> > > >>>> would make more sense to drop support of centos6 so
>>> our
>>> > > >> packages would
>>> > > >>>> use
>>> > > >>>> centos7 with distro packages for tomcat7 and jdk8.
>>> > Should
>>> > > >> also be the
>>> > > >>>> same
>>> > > >>>> with ubuntu 16.04 that use jdk8 and tomcat7 by
>>> default ?
>>> > > >>>>
>>> > > >>>>
>>> > > >>>> thanks,
>>> > > >>>>
>>> > > >>>>
>>> > > >>>>> On Wed, Mar 1, 2017 at 9:01 AM, Rene Moser
>>> > > >> <mail@renemoser.net> wrote:
>>> > > >>>>>
>>> > > >>>>> Hi
>>> > > >>>>>
>>> > > >>>>> While not be directly related to the clodustack
>>> java
>>> > source
>>> > > >> code, any
>>> > > >>>>> RPM created using the specs from the repo e.g. from
>>> > > >> packages/centos7
>>> > > >>>>> and proceeding an upgrade, will hit
>>> CLOUDSTACK-9765, PR
>>> > > >>>>> https://github.com/apache/cloudstack/pull/1923
>>> fixes
>>> > the
>>> > > >> issue.
>>> > > >>>>>
>>> > > >>>>> Regards
>>> > > >>>>> René
>>> > > >>>>>
>>> > > >>>>>
>>> > > >>>>>> On 03/01/2017 02:12 AM, Rajani Karuturi wrote:
>>> > > >>>>>> Hi All,
>>> > > >>>>>>
>>> > > >>>>>> I've created a 4.10.0.0 release, with the
>>> following
>>> > > >> artifacts up
>>> > > >>>> for a
>>> > > >>>>> vote:
>>> > > >>>>>>
>>> > > >>>>>> Git Branch and Commit
>>> > > >>>>>>
>>> > SH:https://git-wip-us.apache.org/repos/asf?p=cloudstack.
>>> > > >>>>> git;a=shortlog;h=refs/heads/4.
>>> 10.0.0-RC20170301T0634
>>> > > >>>>>> Commit:7c1d003b5269b375d87f4f6cfff8a144f0608b67
>>> > > >>>>>> <https://git-wip-us.apache.org
>>> /repos/asf?p=cloudstack
>>> > .
>>> > > >>>>>
>>> > git;a=shortlog;h=refs/heads/4
>>> .10.0.0-RC20170301T0634Commit:
>>> > > >>>>> 7c1d003b5269b375d87f4f6cfff8a144f0608b67>
>>> > > >>>>>>
>>> > > >>>>>> Source release (checksums and signatures are
>>> available
>>> > at
>>> > > >> the same
>>> > > >>>>>>
>>> > > >>
>>> > location):https://dist.apache
>>> .org/repos/dist/dev/cloudstack/
>>> > > >>>> 4.10.0.0/
>>> > > >>>>>>
>>> > > >>>>>> PGP release keys (signed using
>>> > > >>>>>> CBB44821):https://dist.apache.
>>> org/repos/dist/release/
>>> > > >>>> cloudstack/KEYS
>>> > > >>>>>>
>>> > > >>>>>> Vote will be open for 72 hours.
>>> > > >>>>>>
>>> > > >>>>>> For sanity in tallying the vote, can PMC members
>>> > please
>>> > be
>>> > > >> sure to
>>> > > >>>>>> indicate "(binding)" with their vote?
>>> > > >>>>>>
>>> > > >>>>>> [ ] +1 approve
>>> > > >>>>>> [ ] +0 no opinion
>>> > > >>>>>> [ ] -1 disapprove (and reason why)
>>> > > >>>>>>
>>> > > >>>>>>
>>> > > >>>>>>
>>> > > >>>>>> ~Rajani
>>> > > >>>>>> http://cloudplatform.accelerite.com/
>>> > > >>>>>>
>>> > > >>>>>
>>> > > >>>>
>>> > > >>>>
>>> > > >>>>
>>> > > >>
>>> > > >> rohit.yadav@shapeblue.com
>>> > > >> www.shapeblue.com<http://www.shapeblue.com
>>> > ( http://www.shapeblue.com<http://www.shapeblue.com )
>>> > > >> ( http://www.shapeblue.com<http://www.shapeblue.com
>>> )>
>>> > > >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> > > >> @shapeblue
>>> > > >>
>>> > > >> 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.
>>> > > >>
>>> > > >> rohit.yadav@shapeblue.com
>>> > > >> www.shapeblue.com ( http://www.shapeblue.com )
>>> > ( http://www.shapeblue.com )
>>> > > >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> > > >> @shapeblue
>>> > > >>
>>> > > >>
>>> > > >>
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > daan.hoogland@shapeblue.com
>>> > www.shapeblue.com
>>> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> > @shapeblue
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>













Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message