date:20170419

Re: [Github/Gitbox] Setting up your committer account

2017-04-19 Thread Boris Stoyanov

Yup, same here, no GitHub mails recently.. 


boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

> On Apr 19, 2017, at 4:16 AM, Nicolas Vazquez  wrote:
> 
> I noticed the same
> 
> 2017-04-18 12:15 GMT-03:00 Syed Ahmed :
> 
>> Same thing with me. I don't see any github activity on the ML since Friday.
>> 
>> On Tue, Apr 18, 2017 at 5:00 AM, Wido den Hollander 
>> wrote:
>> 
>>> 
 Op 17 april 2017 om 19:58 schreef Sergey Levitskiy <
>>> sergey.levits...@autodesk.com>:
 
 
 I used to receive emails from @dev on every change in git. The last
>>> email came on Friday. Is it expected?
>>> 
>>> I think so? I don't know how that worked previously. There is a
>>> com...@cloudstack.apache.org list though, you mind want to subscribe
>>> there.
>>> 
>>> Wido
>>> 
 Example header:
 
 From: serg38 
 To: 
 References: 
 In-Reply-To: 
 Subject: [GitHub] cloudstack issue #2044: CLOUDSTACK-9877 Cleanup
>>> unlinked templates
 
 Content-type: text/plain;
  charset="UTF-8"
 Content-transfer-encoding: 7bit
 
 Github user serg38 commented on the issue:
 
https://github.com/apache/cloudstack/pull/2044
 
 
 
 On 4/16/17, 10:02 PM, "Rohit Yadav"  wrote:
 
Thanks Wido!
 

From: Wido den Hollander 
Sent: 15 April 2017 15:59:33
To: dev@cloudstack.apache.org
Subject: [Github/Gitbox] Setting up your committer account
 
Hi,
 
Since yesterday we are using the Gitbox [0] services from ASF to
>>> have Github our 'primary' source of code.
 
This means that we can now label PRs, merge them, close them, all
>> on
>>> Github.
 
If you are a committer you have to be added to the 'cloudstack
>>> committers' team on Github and this is done automatically [1] once every
>> X
>>> hours.
 
You however need to make sure that your Apache Profile/ID [2] has
>>> the right information and that you have 2FA [3] enabled on your Github
>>> account.
 
The steps you need to take:
 
- Make sure you are a CloudStack committer
- Make sure you have a Github account
- Enable 2FA [3] on your Github account
- Update your Apache profile [2] and add your Github username
 
Now, after a few hours the sync between ASF and Github should be
>>> completed and you are added to the right team on Github.
 
If that doesn't work you might need to visit the Gitbox setup page
>>> [4] to link your Apache account to Github.
 
Since we moved to Gitbox the URL of our Git repositories also
>>> changed, for example:
 
- https://gitbox.apache.org/repos/asf/cloudstack.git
 
If you want RO you can also sync from Github:
 
- https://github.com/apache/cloudstack.git
 
 
Once you are in the right group on Github you should be able to
>>> label PRs, close them, merge them and move.
 
I have already created [5] a bunch of labels. If we all try to
>> label
>>> the PRs it will be much easier for people to filter PRs and review them.
 
Questions? Ask!
 
Wido
 
[0]: https://gitbox.apache.org/
[1]: https://issues.apache.org/jira/browse/INFRA-13885
[2]: https://id.apache.org/
[3]: https://help.github.com/articles/about-two-factor-
>>> authentication/
[4]: https://gitbox.apache.org/setup/
[5]: https://github.com/apache/cloudstack/labels
 
rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
 
 
 
 
 
>>> 
>>

Re:Re: :[VOTE] Apache Cloudstack 4.10.0.0

2017-04-19 Thread Haijiao

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"写道:



Yes. will do over the weekend.




~ Rajani

http://cloudplatform.accelerite.com/


On April 19, 2017 at 4:07 PM, Haijiao (18602198...@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"写道:


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  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 
> 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 
>> 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"  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
>>>

Re: :[VOTE] Apache Cloudstack 4.10.0.0

2017-04-19 Thread Rajani Karuturi

Yes. will do over the weekend.

~ Rajani

http://cloudplatform.accelerite.com/

On April 19, 2017 at 4:07 PM, Haijiao (18602198...@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"写道:

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
 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

> 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

>> 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" 
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
>>>

Re:Re: :[VOTE] Apache Cloudstack 4.10.0.0

2017-04-19 Thread Haijiao

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"写道:

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  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 
> 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 
>> 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"  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
>>>

Re: [Github/Gitbox] Setting up your committer account

Re:Re: :[VOTE] Apache Cloudstack 4.10.0.0

Re: :[VOTE] Apache Cloudstack 4.10.0.0

Re:Re: :[VOTE] Apache Cloudstack 4.10.0.0

4 matches

Site Navigation

Mail list logo

Footer information