Re: [DISCUSS] Release Apache jclouds 2.6.0 RC1

[Andrew Phillips]

This thread is for discussion of the third release candidate for 
Apache

jclouds 1.6.3.


Many thanks for taking this on, Andrew G!

ap

Re: jclouds Board Report due by Wed Jan 10th - Initial Reminder

[Andrew Phillips]

jclouds, a committee that is due to submit a report by Wed Jan 10th


Argh, only just noticed this (report is due on Wed). Draft page at:

https://cwiki.apache.org/confluence/display/JCLOUDS/2024+-+January+Board+Report+Draft

A belated Happy 2024, everyone!

ap

Re: jclouds Board Report due by Wed Oct 11st - Initial Reminder

[Andrew Phillips]

jclouds, a committee that is due to submit a report by Wed Oct 11st
for the next ASF board meeting.


Draft page at: 
https://cwiki.apache.org/confluence/display/JCLOUDS/2023+-+October+Board+Report+Draft


Please edit as desired!

ap

Fwd: TAC supporting Berlin Buzzwords

[Andrew Phillips]

 Original Message 
Subject: TAC supporting Berlin Buzzwords
Date: 2023-03-24 05:56
From: Gavin McDonald 
To: gmcdon...@apache.org
Reply-To: priv...@jclouds.apache.org

PMCs,

Please forward to your dev and user lists.

Hi All,

The ASF Travel Assistance Committee is supporting taking up to six (6)
people

to attend Berlin Buzzwords In June this year.

This includes Conference passes, and travel & accommodation as needed.

Please see our website at https://tac.apache.org for more information
and how to apply.

Applications close on 15th April.

Good luck to those that apply.

Gavin McDonald (VP TAC)

Re: jclouds Board Report due - Reminder

[Andrew Phillips]

Hi all

FYI that the next board report is due on Jan 11th - skeleton doc here:

https://cwiki.apache.org/confluence/display/JCLOUDS/2023+-+January+Board+Report+Draft

Hope everyone is having a good weekend!

ap

On 2023-01-15 11:59, Sander Striker wrote:

Hi,

According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report for the next ASF board
meeting taking place on January 18th:
  https://www.apache.org/foundation/board/reporting#when

This is a reminder to prepare a report for jclouds and submit it as
described below.  Note that this reminder reaches you later than usual,
if possible please submit a report as soon as possible.

In the Apache governance model, the ASF board delegates responsibility 
for
managing projects to PMCs. This allows projects to govern themselves, 
in

terms of their own development goals, guidelines, and volunteer spirit,
within the scope of our purpose as an open source foundation. The state
allows us to provide an umbrella of corporate protection to our 
projects
and volunteers, but only to the extent that we retain active and 
effective
oversight of each project's operation on behalf of the public's 
interest.


To enable the board to provide oversight across the foundation, each 
PMC

is tasked with providing the board a quarterly report on the health of
their project. This allows us to hear your heartbeat, to see the 
project
through your eyes, and to inform the public through our meeting 
minutes.


Thank you for being a responsible project chair and helping us maintain
oversight over the Apache Software Foundation. If, for whatever reason,
a full report is not possible by the deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we will be reviewing and approving these reports,
asynchronously, during the week prior to our scheduled board meeting.
Reports that haven't received sufficient review will be postponed to 
the
next regular meeting. Please try to submit your report as soon as 
possible.



Submitting your report
--

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal 
observations,

assessment, and ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their 
report:


 a) the Apache Reporter Service
https://reporter.apache.org/

 b) the Whimsy online agenda tool
https://whimsy.apache.org/board/agenda/2023-01-18/jclouds

 c) carefully editing and committing changes to the dated agenda in
https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to bo...@apache.org 
with

Subject: [REPORT] jclouds

If you believe it won't be possible to prepare a report before the 
deadline,
or if the PMC is aware that the Chair is unavailable, please report 
that

and we can reschedule or have someone else report on your behalf.


Attending the Board Meeting
---

The formal board meeting (usually an online videoconference) will be 
held at


  Wed, 18 Jan 2023 at 22:00 UTC

which in other time zones is

  https://timeanddate.com/s/42zn

As always, chairs and ASF members are welcome to attend the board 
meeting.
However, in most cases, we will not be using meeting time to discuss 
reports

unless you specifically request time to speak in person.

During the week prior to the meeting, the directors will read the 
received

reports, make comments (if any) within the agenda tool, discuss those
comments on the board and/or private committee lists, and vote to 
approve.


If we have comments on a report, we will forward them during the
review and attempt to complete any associated action items as well.
This will allow us to be more responsive to project needs and give you
an opportunity to expand on your report if additional details are
requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-

If you want the board to make a decision related to your report, such 
as
changing the chair, establishing a new committee, or allocating a 
budget

for something related to jclouds, you should author a resolution
for that purpose or ask a director to do so for you.

To make this easier, there are several templates we use for common 
board

resolutions. They can be found in

  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2023-01-18/jclouds

If you do place a resolution before the board and that resolution
has not been preapproved before the board meeting, you are encouraged
to attend the meeting in person to address any last-minute questions
or concerns that might arise.

Thanks,
The ASF Board

Fwd: jclouds Board Report due by Wed Oct 12nd - Initial Reminder

[Andrew Phillips]

a committee that is due to submit a report by Wed Oct 12nd


Skeleton page: 
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+October+Board+Report+Draft


Hope everyone is having a good weekend!

ap

Fwd: jclouds Board Report due by Wed Jul 13th - Initial Reminder

[Andrew Phillips]

Hi all

Skeleton board report page: 
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+July+Board+Report+Draft


Regards

ap

 Original Message 
Subject: jclouds Board Report due by Wed Jul 13th - Initial Reminder
Date: 2022-07-05 04:17


Hello,

According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report by Wed Jul 13th
for the next ASF board meeting. This is an initial reminder to prepare a
report for jclouds and submit it as described below.

In the Apache governance model, the ASF board delegates responsibility 
for

managing projects to PMCs. This allows projects to govern themselves, in
terms of their own development goals, guidelines, and volunteer spirit,
within the scope of our purpose as an open source foundation. The state
allows us to provide an umbrella of corporate protection to our projects
and volunteers, but only to the extent that we retain active and 
effective
oversight of each project's operation on behalf of the public's 
interest.


To enable the board to provide oversight across the foundation, each PMC
is tasked with providing the board a quarterly report on the health of
their project. This allows us to hear your heartbeat, to see the project
through your eyes, and to inform the public through our meeting minutes.

Thank you for being a responsible project chair and helping us maintain
oversight over the Apache Software Foundation. If, for whatever reason,
a full report is not possible by the deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we will be reviewing and approving these reports,
asynchronously, during the week prior to our scheduled board meeting.
Reports received after Wed Jul 13th will be postponed to the
next regular meeting. Please try to submit your report early.


Submitting your report
--

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal 
observations,

assessment, and ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their report:

 a) the Apache Reporter Service
https://reporter.apache.org/

 b) the Whimsy online agenda tool
https://whimsy.apache.org/board/agenda/2022-07-20/jclouds

 c) carefully editing and committing changes to the dated agenda in
https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to bo...@apache.org 
with

Subject: [REPORT] jclouds

If you believe it won't be possible to prepare a report before the 
deadline,

or if the PMC is aware that the Chair is unavailable, please report that
and we can reschedule or have someone else report on your behalf.


Attending the Board Meeting
---

The formal board meeting (usually an online videoconference) will be 
held at


  Wed, 20 Jul 2022 at 15:00 UTC

which in other time zones is

  https://timeanddate.com/s/42k8

As always, chairs and ASF members are welcome to attend the board 
meeting.
However, in most cases, we will not be using meeting time to discuss 
reports

unless you specifically request time to speak in person.

During the week prior to the meeting, the directors will read the 
received

reports, make comments (if any) within the agenda tool, discuss those
comments on the board and/or private committee lists, and vote to 
approve.


If we have comments on a report, we will forward them during the
review and attempt to complete any associated action items as well.
This will allow us to be more responsive to project needs and give you
an opportunity to expand on your report if additional details are
requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-

If you want the board to make a decision related to your report, such as
changing the chair, establishing a new committee, or allocating a budget
for something related to jclouds, you should author a resolution
for that purpose or ask a director to do so for you.

To make this easier, there are several templates we use for common board
resolutions. They can be found in

  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2022-07-20/jclouds

If you do place a resolution before the board and that resolution
has not been preapproved before the board meeting, you are encouraged
to attend the meeting in person to address any last-minute questions
or concerns that might arise.

Thanks,
The ASF Board

Fwd: jclouds Board Report due by Wed Apr 13th - Initial Reminder

[Andrew Phillips]

Skeleton board report draft:

https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+April+Board+Report+Draft

Please add/amend as desired!

ap

 Original Message 
Subject: jclouds Board Report due by Wed Apr 13th - Initial Reminder
Date: 2022-03-30 14:33

Re: [ANNOUNCE] Apache jclouds 2.5.0 released

[Andrew Phillips]

The Apache jclouds team is pleased to announce the release of jclouds 
2.5.0.


Many thanks for taking care of this release, Andrew G.!

Regards

ap

Re: [REPORT] jclouds - January 2022

[Andrew Phillips]

Thanks for taking care of this, Andrew G!

ap

On 2022-01-11 07:31, Andrew Gaul wrote:

== Project Status ==

Project successfully released 2.4.0 in Q3 2021.  The team fixed some
modern Java incompatibilities and resolved to streamline the release
process by dropping the labs packages.

There are no issues requiring board attention.

== Community ==

We continue to merge fixes from the community. Apart from this the
overall activity remains low.

Last committer: 2018-07-23 (Daniel Estevez)
Last PMC member: 2021-03-14 (Jean-Baptiste Onofré)

== Community Objectives ==

Release 2.5.0 in Q1 2022.

== Releases ==

The last major jclouds release, 2.4.0, took place on 2021-09-10.
The last bugfix release, 2.2.1, took place on 2020-05-14.

Re: Jclouds AWS S3 Role Based Login

[Andrew Phillips]

Isn't there any way where we don't provide any credentials and during
actual calls blob fetches the credentials (via EC2 token internally)
just like the original AWS (AmazonS3ClientBuilder) client uses.


As far as I am aware, this is not currently possible, no. 
https://github.com/jclouds/legacy-jclouds/issues/1280 seems like a 
feature request for this, but it was not implemented.


What the AWS libraries are doing, as you point out, is fetching the 
token internally before making any calls. The Stack Overflow example 
demonstrates how one can do this using jclouds, but using STS.


For the instance profile, I think what would be needed is something 
like:


1) Get an instance of the the instance profile API (this is in 
jclouds-labs-aws)

2) Use this instance to pull credentials from the machine when needed
3) Pass the credentials retrieved in 2) to jclouds via a 
Supplier


I haven't tried this myself, though - hopefully someone on this thread 
is able to provide a code example, or other ways in which this can (or 
cannot) be made to work!


Regards

ap

Re: Jclouds AWS S3 Role Based Login

[Andrew Phillips]

could hopefully be made to work for instance profile credentials


Based on a quick glance at the code, the InstanceProfileApi (note: in 
jclouds-labs-aws) may be useful here:


https://github.com/apache/jclouds-labs-aws/blob/master/iam/src/main/java/org/jclouds/iam/features/InstanceProfileApi.java

Regards

ap

On 2022-01-11 04:47, Andrew Phillips wrote:

Hi Abhinav

Is there a way to not provide the below .credentials and the context 
pulls via

Instance Profile Credentials.


This sounds like https://github.com/jclouds/legacy-jclouds/issues/1280
(note: in the legacy repo, which is no longer in use) - I'm not sure
if something like that was ever implemented, though.

Here is a code snippet using STS to provide credentials in a different 
way:


https://stackoverflow.com/questions/23520216/using-aws-s3-via-jclouds-how-to-assume-role

Something like that (i.e. creating an appropriate custom
credentialsSupplier) could hopefully be made to work for instance
profile credentials, too?

Regards

ap

Re: Jclouds AWS S3 Role Based Login

[Andrew Phillips]

Hi Abhinav

Is there a way to not provide the below .credentials and the context 
pulls via

Instance Profile Credentials.


This sounds like https://github.com/jclouds/legacy-jclouds/issues/1280 
(note: in the legacy repo, which is no longer in use) - I'm not sure if 
something like that was ever implemented, though.


Here is a code snippet using STS to provide credentials in a different 
way:


https://stackoverflow.com/questions/23520216/using-aws-s3-via-jclouds-how-to-assume-role

Something like that (i.e. creating an appropriate custom 
credentialsSupplier) could hopefully be made to work for instance 
profile credentials, too?


Regards

ap

Re: jclouds Board Report due by Wed Jan 12nd - Initial Reminder

[Andrew Phillips]

Hi all

Skeleton report here: 
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+January+Board+Report+Draft


Please add comments as desired!

ap


Happy New Year!

According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report by Wed Jan 12nd
for the next ASF board meeting. This is an initial reminder to prepare 
a

report for jclouds and submit it as described below.

In the Apache governance model, the ASF board delegates responsibility 
for
managing projects to PMCs. This allows projects to govern themselves, 
in

terms of their own development goals, guidelines, and volunteer spirit,
within the scope of our purpose as an open source foundation. The state
allows us to provide an umbrella of corporate protection to our 
projects
and volunteers, but only to the extent that we retain active and 
effective
oversight of each project's operation on behalf of the public's 
interest.


To enable the board to provide oversight across the foundation, each 
PMC

is tasked with providing the board a quarterly report on the health of
their project. This allows us to hear your heartbeat, to see the 
project
through your eyes, and to inform the public through our meeting 
minutes.


Thank you for being a responsible project chair and helping us maintain
oversight over the Apache Software Foundation. If, for whatever reason,
a full report is not possible by the deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we will be reviewing and approving these reports,
asynchronously, during the week prior to our scheduled board meeting.
Reports received after Wed Jan 12nd will be postponed to the
next regular meeting. Please try to submit your report early.


Submitting your report
--

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal 
observations,

assessment, and ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their 
report:


 a) the Apache Reporter Service
https://reporter.apache.org/

 b) the Whimsy online agenda tool
https://whimsy.apache.org/board/agenda/2022-01-19/jclouds

 c) carefully editing and committing changes to the dated agenda in
https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to bo...@apache.org 
with

Subject: [REPORT] jclouds

If you believe it won't be possible to prepare a report before the 
deadline,
or if the PMC is aware that the Chair is unavailable, please report 
that

and we can reschedule or have someone else report on your behalf.


Attending the Board Meeting
---

The formal board meeting (usually an online videoconference) will be 
held at


  Wed, 19 Jan 2022 at 22:00 UTC

which in other time zones is

  https://timeanddate.com/s/42eg

As always, chairs and ASF members are welcome to attend the board 
meeting.
However, in most cases, we will not be using meeting time to discuss 
reports

unless you specifically request time to speak in person.

During the week prior to the meeting, the directors will read the 
received

reports, make comments (if any) within the agenda tool, discuss those
comments on the board and/or private committee lists, and vote to 
approve.


If we have comments on a report, we will forward them during the
review and attempt to complete any associated action items as well.
This will allow us to be more responsive to project needs and give you
an opportunity to expand on your report if additional details are
requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-

If you want the board to make a decision related to your report, such 
as
changing the chair, establishing a new committee, or allocating a 
budget

for something related to jclouds, you should author a resolution
for that purpose or ask a director to do so for you.

To make this easier, there are several templates we use for common 
board

resolutions. They can be found in

  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2022-01-19/jclouds

If you do place a resolution before the board and that resolution
has not been preapproved before the board meeting, you are encouraged
to attend the meeting in person to address any last-minute questions
or concerns that might arise.

Thanks,
The ASF Board

Re: jclouds-labs

[Andrew Phillips]

Also +1 - thanks for kicking off this thread!

ap

Re: jclouds Board Report due by Wed Oct 13th - Initial Reminder

[Andrew Phillips]

due to submit a report by Wed Oct 13th for the next ASF board meeting. 
This is an initial reminder to prepare a report for jclouds and submit 
it as described below.


Skeleton page at 
https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+October+Board+Report+Draft


Have a good weekend, all!

ap

Re: [ANNOUNCE] Apache jclouds 2.4.0 released

[Andrew Phillips]

Thanks for dealing with this Andrew G.!!


Big +1 - thank you, Andrew G.!

ap

Re: jclouds 2.4.0 planning

[Andrew Phillips]

It has been 5 months since jclouds 2.3.0 and I would like to plan to

release 2.4.0 next month.

Thanks for kicking this off, Andrew G!

ap

Re: Remove Google AppEngine driver?

[Andrew Phillips]

If no one else volunteers to fix this I suggest that we remove it.


+1 to removing unless someone is interested in getting it working.

Thanks for suggesting this, Andrew G!

ap

Re: [CONF] Apache jclouds > 2021 - July Board Report Draft

[Andrew Phillips]

There's 1 new edit on your page


Thanks for taking care of this, Andrew G!

ap

Fwd: jclouds Board Report due by Wed Jul 14th - Initial Reminder

[Andrew Phillips]

Subject: jclouds Board Report due by Wed Jul 14th - Initial Reminder


Skeleton report at 
https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+July+Board+Report+Draft


Regards

ap

Re: April board report

[Andrew Phillips]

It looks good to me. Short and precise.


+1 - thanks for putting this together, Gaul!

ap

Re: [DISCUSS] Release Apache jclouds 2.3.0 RC1

[Andrew Phillips]

+1 (binding)


@Jean-Baptiste: as a technicality, I think yours would be a non-binding 
vote - my understanding was that only votes by PMC members are binding 
[1, 2]?


Thank you of course for taking the time to test the RC!

ap

[1] 
http://www.apache.org/legal/release-policy.html#:~:text=For%20a%20release%20vote%20to,by%20PMC%20members%20are%20binding.

[2] https://projects.apache.org/committee.html?jclouds

Re: Change the jclouds chair

[Andrew Phillips]

Andrew Gaul. is quite more active and involved in the project than I 
am, so

I'd like to propose him as the new chair for the project.


+1 - thanks for the suggestion!

@Gaul: glad to hear that you might be available for this!

A belated Happy 2021, everyone

ap

Fw: jclouds Board Report due by Wed Jan 13th - Initial Reminder

[Andrew Phillips]

jclouds, a committee that is due to submit a report by Wed Jan 13th
for the next ASF board meeting.


Skeleton report here:

https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+January+Board+Report+Draft

Please edit as desired. And, of course, a belated Happy 2021, everyone!!

ap

Re: jclouds 2.3.0

[Andrew Phillips]

Thanks for taking the lead on this!


+1 - thanks!

ap

Fwd: jclouds Board Report due by Wed Oct 14th - Initial Reminder

[Andrew Phillips]

Skeleton draft: 
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+October+Board+Report+Draft


Please add/amend as desired!

ap

 Original Message 
Subject: jclouds Board Report due by Wed Oct 14th - Initial Reminder
Date: 2020-10-05 12:42

Hello,

According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report by Wed Oct 14th
for the next ASF board meeting. This is an initial reminder to prepare a
report for jclouds and submit it as described below.

Re: [IMPORTANT] Jenkins jobs need to be migrated in 2 weeks

[Andrew Phillips]

The next step will be to see what we learn from INFRA-20725, and then
to hopefully close things out from there.


Just closing this out with the list of warnings [1] related to the 
migrated jobs. At a first glance, none of them seem critical, and a 
number of the affected jobs are currently deactivated [2].


hudson.maven.MavenModuleSet 
JClouds/jclouds-with-credentials/jclouds-chef-live-tests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/jclouds-karaf MissingFieldException: 
No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-pull-request-jobs/jclouds-labs-openstack-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-with-credentials/jclouds-packet-live-tests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty', 
MissingFieldException: No field 'textParamValueOnNewLine' found in class

 'hudson.plugins.parameterizedtrigger.PredefinedBuildParameters'

hudson.maven.MavenModuleSet JClouds/jclouds-cli MissingFieldException: 
No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-pull-request-jobs/jclouds-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.model.FreeStyleProject 
JClouds/jclouds-pull-request-jobs/jclouds-site-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty', 
MissingFieldException: No field 'textParamValueOnNewLine' found in class 
'hudson.plugins.parameterizedtrigger.PredefinedBuildParameters'


hudson.maven.MavenModuleSet JClouds/jclouds-labs-aws 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/jclouds-2.1.x/jclouds-karaf-2.1.x 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


com.cloudbees.hudson.plugins.folder.Folder 
JClouds/jclouds-with-credentials CannotResolveClassException: 
de.fspengler.hudson.pview.ConsoleViewColumn, 
CannotResolveClassException: 
hudson.plugins.lastsuccessdescriptioncolumn.LastSuccessDescriptionColumn, 
CannotResolveClassException: 
de.fspengler.hudson.pview.ConsoleViewColumn, 
CannotResolveClassException: 
hudson.plugins.lastsuccessdescriptioncolumn.LastSuccessDescriptionColumn, 
CannotResolveClassException: 
de.fspengler.hudson.pview.ConsoleViewColumn, 
CannotResolveClassException: 
hudson.plugins.lastsuccessdescriptioncolumn.LastSuccessDescriptionColumn


hudson.maven.MavenModuleSet 
JClouds/jclouds-with-credentials/jclouds-google-compute-engine-live-tests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/jclouds-2.1.x/jclouds-cli-2.1.x 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.matrix.MatrixProject JClouds/jclouds-compat 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-pull-request-jobs/jclouds-pull-requests-manual 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/2.2.x/jclouds-2.2.x 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/2.2.x/jclouds-labs-aws-2.2.x 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-pull-request-jobs/jclouds-labs-aws-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet JClouds/jclouds-2.1.x/jclouds-labs-aws-2.1.x 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.maven.MavenModuleSet 
JClouds/jclouds-pull-request-jobs/jclouds-karaf-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 
'org.datadog.jenkins.plugins.datadog.DatadogJobProperty'


hudson.model.FreeStyleProject 
JClouds/jclouds-with-credentials/jclouds-site-pull-requests 
MissingFieldException: No field 'emitOnCheckout' found in class 

Re: [IMPORTANT] Jenkins jobs need to be migrated in 2 weeks

[Andrew Phillips]

The next step will be to see what we learn from INFRA-20725, and then
to hopefully close things out from there.


I should add a shout-out here to Gavin McDonald, who's responded very 
quickly to all the Infra issues. Many thanks, Gavin! Also, of course, 
for giving us the extra week in which to get this done! ;-)


ap

Re: [IMPORTANT] Jenkins jobs need to be migrated in 2 weeks

[Andrew Phillips]

Hi all

A quick update here: all jobs have now been migrated to 
https://ci-builds.apache.org/job/JClouds/ - you should be able to log in 
using your ASF ID to modify jobs if needed.


As suggested in the instructions I followed [1], I've opened INFRA-20725 
to see if there are any configuration elements that the new Jenkins 
server did not understand, so we can potentially identify missing 
plugins, and ask for them to be installed.


Some of the jobs - surprisingly, perhaps - already seem to be working. 
Many, especially those that require credentials, will likely need tweaks 
(see also [1]); if anyone can help out with that, that'd be much 
appreciated. The pull request [3] jobs are also currently (still) 
disabled.


The next step will be to see what we learn from INFRA-20725, and then to 
hopefully close things out from there. At least we now have our job 
configurations ported over.


Regards

ap

[1] 
https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees

[2] https://issues.apache.org/jira/browse/INFRA-20725
[3] 
https://ci-builds.apache.org/job/JClouds/job/jclouds-pull-request-jobs/

Re: Jenkins instance builds.a.o being shut down 22nd August.

[Andrew Phillips]

Hi Gavin

Sorry to be bugging you again (and happy to continue this on 
users@infra.a.o if preferred) - it seems as though builds.a.o is 
currently down, though :-(


I've opened INFRA-20716 [1] for this; if there's any way to easily bring 
it back, that'd be much appreciated. We'd then be keen to continue 
migrating our jobs away from it.


Thanks in advance!

ap

[1] https://issues.apache.org/jira/browse/INFRA-20716

Re: Jenkins instance builds.a.o being shut down 22nd August.

[Andrew Phillips]

Hi Gavin


The deadline has - for one time only - been extended to 22nd August -
so you have 1 more week only to move your jobs.


Thanks for the reminder, and for the generous extension! As a first step 
to trying to make something happen before then, we have opened 
INFRA-20695 [1] to ask for a destination for the jclouds-related jobs to 
be created.


Given the short timeframe, is there anything we could do to potentially 
accelerate this? Of course, if there's any way we can help out with 
that, please let us know!


Regards

ap

[1] https://issues.apache.org/jira/browse/INFRA-20695

Re: [IMPORTANT] Jenkins jobs need to be migrated in 2 weeks

[Andrew Phillips]

We need to migrate the Jenkins instance or rely on another build 
system,

such as Travis, or GH actions.


I'm going to try the instructions at [1] to see how much we can move to 
ci-builds.a.o. I'll probably only have limited time to try to fix any 
broken builds, but at least we'll hopefully be able to retain the 
configurations.


Opened https://issues.apache.org/jira/browse/INFRA-20695 as a first 
step.


Have a good weekend, all!

ap

[1] 
https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees

Re: Build failed in Jenkins: jclouds-with-credentials » mirror-apache-to-jclouds #38260

[Andrew Phillips]

I disable the periodic build.  This is no longer necessary since we
archived the non-Apache repository.


Ack - thanks for the heads-up!

ap

Re: jclouds Board Report due by Wed Jul 8th - Initial Reminder

[Andrew Phillips]

Report sent.


Thanks, all!

ap

Fwd: jclouds Board Report due by Wed Jul 8th - Initial Reminder

[Andrew Phillips]

Hi all

July's board report is due next week (see below). Skeleton page at 
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+July+Board+Report+Draft


Regards

ap

 Original Message 
Subject: jclouds Board Report due by Wed Jul 8th - Initial Reminder
Date: 2020-06-29 20:17
From: "Roy T. Fielding" 
To: Ignasi Barrera 
Copy: priv...@jclouds.apache.org
Reply-To: priv...@jclouds.apache.org

Hello,

According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report by Wed Jul 8th
for the next ASF board meeting. This is an initial reminder to prepare a
report for jclouds and submit it as described below.

Thank you for being a responsible project chair and helping us maintain
oversight over the Apache Software Foundation. If, for whatever reason,
a full report is not possible by the deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we have initiated a new process for reviewing
and approving these reports, asynchronously, during the week prior
to our scheduled board meeting.

Reports received after Wed Jul 8th will be postponed to the
next regular meeting. Please try to submit your report much earlier.


Submitting your report
--

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal 
observations,

assessment, and ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their report:

 a) the Apache Reporter Service
https://reporter.apache.org/

 b) the Whimsy online agenda tool
https://whimsy.apache.org/board/agenda/2020-07-15/jclouds

 c) carefully editing and committing changes to the dated agenda in
https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to bo...@apache.org 
with

Subject: [REPORT] jclouds

If you believe it won't be possible to prepare a report before the 
deadline,

or if the PMC is aware that the Chair is unavailable, please report that
and we can reschedule or have someone else report on your behalf.


Attending the Board Meeting
---

The formal board meeting (usually an online videoconference) will be 
held at


  Wed, 15 Jul 2020 at 12:30 UTC

which in other time zones is

  https://timeanddate.com/s/429u

As always, chairs and ASF members are welcome to attend the board 
meeting.
However, in most cases, we will not be using meeting time to discuss 
reports

unless you specifically request time to speak in person.

During the week prior to the meeting, the directors will read the 
received

reports, make comments (if any) within the agenda tool, discuss those
comments on the board and/or private committee lists, and vote to 
approve.


If we have comments on a report, we will forward them during the
review and attempt to complete any associated action items as well.
This will allow us to be more responsive to project needs and give you
an opportunity to expand on your report if additional details are
requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-

If you want the board to make a decision related to your report, such as
changing the chair, establishing a new committee, or allocating a budget
for something related to jclouds, you should author a resolution
for that purpose or ask a director to do so for you.

To make this easy, there are several templates we use for common board 
resolutions. They can be found in


  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2020-07-15/jclouds

If you do place a resolution before the board and that resolution
has not been preapproved before the board meeting, you are encouraged
to attend the meeting in person to address any last-minute questions
or concerns that might arise.

Thanks,
The ASF Board

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

[Andrew Phillips]

[moving this here from the VOTE thread...]

Sorry, I have little expertise with gpg.  I believe this is the same 
key

I have used since 2017.  Does this mean that my key is not signed by
anyone in a chain of trust?  This should not block the release, right?


I don't think this is a release blocker, no - the key is the one listed 
in the KEYS file, which I think is what we're checking for. Just wanted 
to mention it as a heads-up.


Regards

ap

Re: [VOTE] Release Apache jclouds 2.2.1 RC1

[Andrew Phillips]

===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Checklist (all items optional, mark only those personally verified):

[X] PGP signatures are valid.
[ ] Expanded source archive matches contents of RC tag.
[ ] Expanded source archive builds and passes tests.
[X] LICENSE is present and correct.
[X] NOTICE is present and correct, including copyright date.
[ ] All files have license headers where appropriate.
[ ] All dependencies have compatible licenses.
[X] No compiled archives bundled in source archive.
[ ] I follow this project's commits list.
---
Notes:
* Signing key C7F10751 is included in 
https://downloads.apache.org/jclouds/KEYS but does not seem to be 
published publicly, resulting in this warning:


gpg: Good signature from "Andrew Gaul "
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the

* Did not verify SHA512 checksums
* Checked for compiled archives by searching for ".jar", ".bin",
".zip" and ".tar.gz" in the expanded source archives
* Unable to run 'mvn clean install -Dmaven.javadoc.skip=true', and thus 
unable to rely on the RAT plugin's execution to verify licenses and 
headers


Thanks to Gaul for getting this release out, and to everyone who tested 
for helping out!


Regards

ap

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

[Andrew Phillips]

Hi JB

Just as a matter of procedure, I think your vote may technically be 
"non-binding" rather than "binding"?


If you were able to run the verification script successfully (I'm still 
wrestling with my local system), I'd be happy to take that information 
into account in my upcoming vote.


Thanks for taking the time to test the release!

ap

Re: future of jclouds

[Andrew Phillips]

Given the comments so far, would it make sense to consider:

1. Move to (only) Java 8
2. Update library dependencies

as the top 2 issues to focus on?

Regards

ap

Re: future of jclouds

[Andrew Phillips]

Some ideas:

* spin out components, similar to what we did with jclouds-karaf 
previously
* release from master and stop maintaining release branches, e.g., 
2.2.x

* reduce the Java compatibility matrix, e.g., Java 8 and newer only
* upgrade key dependencies, e.g., BouncyCastle, Guava, to avoid
  dependency headaches
* graduate more providers in labs


These all seem reasonable to me - do you have any gut feel estimate of 
which would reduce the burden the most?


Regards

ap

Re: 2.2.1 release

[Andrew Phillips]

I propose releasing 2.2.1 in next week since it has been 6 months since

2.2.0.

+1 - thanks for suggesting this! Should be able to help with release 
testing if needed, too.


Have a good Sunday, everyone!

ap

Re: Fw: jclouds Board Report due for April 2020 - Initial Reminder

[Andrew Phillips]

I've updated it and will be sending it in a bit


Thanks, as usual, for taking care of this, Ignasi!

Hope everyone's having a good weekend...

ap

Re: Fw: jclouds Board Report due for April 2020 - Initial Reminder

[Andrew Phillips]

Hi all

A quick follow-up here, in case anyone has anything they'd like to add - 
the report submission is technically already a little overdue (meeting 
itself is next Wed).


Regards

ap

On 2020-03-25 21:18, Andrew Phillips wrote:
This email was sent on behalf of the ASF Board.  It is an initial 
reminder

to give you plenty of time to prepare the report.


Skeleton page here:

https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+April+Board+Report+Draft

Please edit as needed.

Hope everyone is doing as well as possible under the circumstances!

ap

Fw: jclouds Board Report due for April 2020 - Initial Reminder

[Andrew Phillips]

This email was sent on behalf of the ASF Board.  It is an initial 
reminder

to give you plenty of time to prepare the report.


Skeleton page here:

https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+April+Board+Report+Draft

Please edit as needed.

Hope everyone is doing as well as possible under the circumstances!

ap

Re: Fw: jclouds Board Report due for January 2020 - Initial Reminder

[Andrew Phillips]

A quick follow-up ping on this - officially due tomorrow.

Regards

ap

On 2020-01-04 08:35, Andrew Phillips wrote:

Skeleton template for January's report, which is due *next Wednesday*:

https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+January+Board+Report+Draft

Happy New Year, everyone!!

ap

Fw: jclouds Board Report due for January 2020 - Initial Reminder

[Andrew Phillips]

Skeleton template for January's report, which is due *next Wednesday*:

https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+January+Board+Report+Draft

Happy New Year, everyone!!

ap

Re: EOL 2.1.x

[Andrew Phillips]

I think we should assume the EOL of the 2.1.x branch and do not 
cherry-pick

issues there unless they are critical security issues.


+1 to that from me, too.

ap

Re: Fwd: jclouds Board Report due for October 2019 - Initial Reminder

[Andrew Phillips]

Done and sent.


Many thanks for the detailed additions and for taking care of this, 
Ignasi!


ap

Re: Fwd: jclouds Board Report due for October 2019 - Initial Reminder

[Andrew Phillips]

Hi all

A quick reminder that the report is officially due on Thu (day after 
tomorrow) - please edit as appropriate!


Regards

ap


Hi all

Here the traditional skeleton page for the Oct report that's due next 
week:


https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+October+Board+Report+Draft

Please edit as appropriate!

Regards

ap

 Original Message 
Subject: jclouds Board Report due for October 2019 - Initial Reminder
Date: 2019-09-29 21:18


This email was sent on behalf of the ASF Board.  It is an initial 
reminder to

give you plenty of time to prepare the report.

According to board records, you are listed as the chair of a committee 
that is

due to submit a report this month. [1] [2]

The meeting is scheduled for Wed, 16 Oct 2019 at 10:30 PDT and the 
deadline for

submitting your report is 1 full week prior to that (Wed Oct 9th)!

Meeting times in other time zones:

  https://timeanddate.com/s/3zj0

Please submit your report with sufficient time to allow the board 
members
to review and digest. Again, the very latest you should submit your 
report

is 1 full week (7days) prior to the board meeting (Wed Oct 9th).

Re: Cut a release

[Andrew Phillips]

Will there be energy and availability to vote it?


I'll try to help out if needed. Thanks for bringing this up and taking 
this on, Ignasi!


Regards

ap

Fwd: jclouds Board Report due for October 2019 - Initial Reminder

[Andrew Phillips]

Hi all

Here the traditional skeleton page for the Oct report that's due next 
week:


https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+October+Board+Report+Draft

Please edit as appropriate!

Regards

ap

 Original Message 
Subject: jclouds Board Report due for October 2019 - Initial Reminder
Date: 2019-09-29 21:18


This email was sent on behalf of the ASF Board.  It is an initial 
reminder to

give you plenty of time to prepare the report.

According to board records, you are listed as the chair of a committee 
that is

due to submit a report this month. [1] [2]

The meeting is scheduled for Wed, 16 Oct 2019 at 10:30 PDT and the 
deadline for

submitting your report is 1 full week prior to that (Wed Oct 9th)!

Meeting times in other time zones:

  https://timeanddate.com/s/3zj0

Please submit your report with sufficient time to allow the board 
members
to review and digest. Again, the very latest you should submit your 
report

is 1 full week (7days) prior to the board meeting (Wed Oct 9th).

Re: Delivery date of JClouds 2.1.2

[Andrew Phillips]

I'm personally interested in knowing how old is this release.


The date of the announcement email was 2019-02-06:

http://mail-archives.apache.org/mod_mbox/jclouds-dev/201902.mbox/browser

I've opened a PR to fix the incorrect year on the site [1]. Thanks for 
catching that!


Regards

ap

[1] https://github.com/apache/jclouds-site/pull/9/files

Re: jclouds Board Report due for July 2019 - Initial Reminder

[Andrew Phillips]

I've updated https://cwiki.apache.org/confluence/x/WCsyBw please help
me out integrating/editing it as you see fit.


Made a few small tweaks - thanks for putting that together!

Regards


ap

Re: jclouds Board Report due for July 2019 - Initial Reminder

[Andrew Phillips]

> The meeting is scheduled for Wed, 17 Jul 2019 at 10:30 PDT and the> deadline 
> for submitting your report is 1 full week prior to that> (Wed Jul 10th)!
As per usual, here a skeleton page for the report:
https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+July+Board+Report+Draft
Regards
ap

Re: [VOTE] Move jclouds-karaf and jclouds-cli projects under Karaf project governance

[Andrew Phillips]

[x] +1 Approve the change

Fwd: jclouds Board Report due for April 2019 - Initial Reminder

[Andrew Phillips]

The meeting is scheduled for Wed, 17 Apr 2019 at 10:30 PDT and the
deadline for submitting your report is 1 full week prior to that (Wed
Apr 10th)!


Argh, totally missed this notification :-( Created the usual skeleton 
page here:


https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+April+Board+Report+Draft

Deadline is officially tomorrow, but hope we'll be able to get this in 
even if it's a little closer to the actual board meeting date.


Regards

ap

Re: [HEADS UP] Update to Apache Karaf 4.2.x & provisioning proposal

[Andrew Phillips]

I will open the PR during the week end.


Great, thank you!!

ap

Re: [GitHub] gaul opened a new pull request #1: Remove stale Meetup link

[Andrew Phillips]

infra jira ticket please


Done!

https://issues.apache.org/jira/browse/INFRA-17608

Regards

ap

Re: [GitHub] gaul opened a new pull request #1: Remove stale Meetup link

[Andrew Phillips]

Forwarding to users@infra...

ap


I don't think we want all these automated mails going to dev@; instead
they should go to notifications@.  Does anyone know how we can change
this?

On Wed, Jan 09, 2019 at 09:00:37PM -, GitBox wrote:

gaul opened a new pull request #1: Remove stale Meetup link
URL: https://github.com/apache/jclouds-site/pull/1





This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [HEADS UP] Update to Apache Karaf 4.2.x & provisioning proposal

[Andrew Phillips]

For the second part about provisioning feature, I need to do some
cleanup on the PoC before starting a concrete discussion.


Thanks for the update - looking forward to hearing more about these 
ideas!


Regards

ap

Re: Newly added C5 Instance Type do not supports c5d series of AWS

[Andrew Phillips]

[forwarding to Karim - @Karim, you may want to sign up to the mailing 
list for this conversation]


On 2018-11-21 18:13, Ignasi Barrera wrote:

HI Kazim,

The best way to move forward and get things done is... just go ahead 
and do

them :)

If you look at JCLOUDS-1387 and the pull request that fixes it, you'll 
see
that adding the missing instance types is quite easy. Would you want to 
add

them and send a pull request? (We'll be happy to help and assist) That
would be very much appreciated and definitely the fastest way to get 
that

fixed.


Regards,

I.


On Wed, 21 Nov 2018 at 22:57, Kazim Raza 
wrote:


Hi Devs,


There is a recent enhancement being done (JCLOUDS-1387<
https://issues.apache.org/jira/browse/JCLOUDS-1387> ) to support C5 & 
M5
AWS instance types that do not supports the complete series, If you 
check
the whole list here at: AWS 
https://aws.amazon.com/ec2/instance-types/c5/


JClouds version 2.1.1 is missing AWS InstanceTypes c5d.large to
c5d.18xlarge.


Can anyone of you please let me know the way to move forward? We 
wanted to

use one of the C5d / M5d AWS Instance Types but couldn't be able to
provision it using JCLOUDS. I have cut a JIRA ticket on JCLOUDS here 
as:

https://issues.apache.org/jira/browse/JCLOUDS-1467


Awaiting your response on that matter.


Thanks,

Kazim

Re: [HEADS UP] Update to Apache Karaf 4.2.x & provisioning proposal

[Andrew Phillips]

On the other hand, I was thinking about adding a Provisioning/Compute
Service for Karaf. The idea is to easily provision and bootstrap 
Apache

Karaf runtime (vanilla or custom) on a cloud provider.


If I understand this correctly, the idea is firstly to use jclouds to 
install (?) a Karaf runtime on a cloud provider, then expose that 
runtime as a compute service in its own right?


That would be an interesting idea that I don't think has been tried 
previously - in what sense (question from someone with little Karaf 
background here) does Karaf fit the model of a cloud compute service? 
What type of "things" can you provision in Karaf, for example?


Regards

ap

Fwd: jclouds Board Report due for October 2018 - Initial Reminder

[Andrew Phillips]

Hi all

Skeleton page for our Oct board report draft here:

https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+October+Board+Report+Draft

As noted, the official date on which Daniel became the latest committer 
may need to be tweaked since I can't find an [ANNOUNCE] email for that.


Hope everyone's having a good Sunday!

ap

Re: Remove offending commit from jclouds repo (INFRA-16889)

[Andrew Phillips]

* Since we will be pushing -mirror to the SF remote, will that trigger

an email notification for each commit object pushed? (That would be
potentially a huge email flood.

Could we perhaps temporarily direct notifications to a different email 
group? That way, we could even preserve them if a record is needed, but 
would not flood the "actual" notification list.


Also, I just wanted to verify that, as far as I understand, the proposal 
does *not* involve changing any commit IDs for commits reachable from 
branches?


Regards

ap

Re: [VOTE] Release Apache jclouds 2.1.1 RC1

[Andrew Phillips]

Hi all

===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Checklist (all items optional, mark only those personally verified):

[X] Checksums and PGP signatures are valid.
[ ] Expanded source archive matches contents of RC tag.
[ ] Expanded source archive builds and passes tests.
[X] LICENSE is present and correct.
[X] NOTICE is present and correct, including copyright date.
[X] All files have license headers where appropriate.
[X] All dependencies have compatible licenses.
[X] No compiled archives bundled in source archive.
[ ] I follow this project's commits list.
---
Notes:
* Ran 'mvn clean install -Dmaven.javadoc.skip=true', which includes
the RAT plugin execution.
* Checked for compiled archives by searching for ".jar", ".bin",
".zip" and ".tar.gz" in the expanded source archives
* Mentioned minor test failures in the [DISCUSS] thread
* Built the blobstore-basics example in jclouds-examples and ran it 
successfully against aws-s3


Many thanks to Ignasi for getting this RC out!

ap

Re: [DISCUSS] Release Apache jclouds 2.1.1 RC1

[Andrew Phillips]

Hi all

Seeing a couple of test failures on Windows:

* 
FilesystemStorageStrategyImplTest.testDeletingInvalidPathFileEndsNormally 
in filesystem


This is a known issue [1], although hopefully we are a little further to 
figuring out what the behaviour should be. Added a comment to the PR [2] 
to that effect.


* StaticLargeObjectApiMockTest.testReplaceManifestUnicodeUTF8 in 
openstack-swift


Here, the error message seems to indicate some incorrect decoding 
("unic?de" vs. "unicÔé¬de"); not clear if/how that would be related to 
Windows:


testReplaceManifestUnicodeUTF8(org.jclouds.openstack.swift.v1.features.StaticLar
geObjectApiMockTest)  Time elapsed: 0.122 sec  <<< FAILURE!
java.lang.AssertionError: expected 
[[{"path":"/mycontainer/unic?de/slo/1","etag"

:"0228c7926b8b642dfb29554cd1f00963","size_bytes":1468006},{"path":"/mycontainer/
unic?de/slo/2","etag":"5bfc9ea51a00b790717eeb934fb77b9b","size_bytes":1572864},{
"path":"/mycontainer/unic?de/slo/3","etag":"b9c3da507d2557c1ddc51f27c54bae51","s
ize_bytes":256}]] but found 
[[{"path":"/mycontainer/unicÔé¬de/slo/1","etag":"022

8c7926b8b642dfb29554cd1f00963","size_bytes":1468006},{"path":"/mycontainer/unicÔ
é¬de/slo/2","etag":"5bfc9ea51a00b790717eeb934fb77b9b","size_bytes":1572864},{"pa
th":"/mycontainer/unicÔé¬de/slo/3","etag":"b9c3da507d2557c1ddc51f27c54bae51","si
ze_bytes":256}]]

This all using the following setup:

Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 
2014-02-14T12:37:5

2-05:00)
Maven home: C:\Program Files (x86)\Apache\maven-3.2.1\bin\..
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_40\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

The test failures are minor and, from my perspective, shouldn't block 
the release.


Regards

ap

[1] https://issues.apache.org/jira/browse/JCLOUDS-1361
[2] https://github.com/jclouds/jclouds/pull/1162#discussion_r210170364

Hello "gclouds" (well, almost...)

[Andrew Phillips]

Hi all

FYI on "Go cloud" - a/the new multi-cloud abstraction for Go:

https://blog.golang.org/go-cloud

So close with the name there! ;-)

Regards

ap

Skeleton for July board report

[Andrew Phillips]

Hi all

I've created the "traditional skeleton page" for the July board report, 
which is due on the 11th:


https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+July+Board+Report+Draft

Please edit as needed!

Regards

ap

Re: jclouds report

[Andrew Phillips]

I've added some notes to April's report at [1]


Thanks, Andrea! I've made some minor text edits, but the content overall 
should be unchanged. One point regarding the paragraph about Dimension, 
1&1 and Aliyun: there was some previous board feedback about how to 
refer to companies in the public section of board reports, but I don't 
recall if the guidance to mention companies by name in a  
section only applied to concerns, or to all company mentions in general.


Ignasi, Andrew G., do you happen to recall what the advice there was?

Regards

ap

Re: archive legacy-jclouds repositories

[Andrew Phillips]

I archived all the legacy-jclouds repositories today.


Thanks for taking care of that!

ap

Re: Jenkins build is back to normal : jclouds-aggregate-javadocs #1063

[Andrew Phillips]

That would be much better! :D


I tried that with the original setup and then needed to mess around a 
bit to get some Python library incompatibilities to work, but in the end 
it worked out.


Your version with the cURL call (but minus the need to compile OpenSSL 
and cURL) is actually quicker and simpler, but sticking with the 
original Python script probably gives us more room to do different 
things with the comment should we wish to in future. Either variant 
works for me, though.


Regads

ap

Re: Jenkins build is back to normal : jclouds-aggregate-javadocs #1063

[Andrew Phillips]

We don't have root/sudo root access to upgrade or install libs in the
slave, so I've modified the build to download and compile the latest
OpenSSL version


Argh, I should have explained the issue with the Javadocs build, which 
had the same problem (amongst other things). An alternative solution is 
to tag the job with "lxc-fedora25"; then it will run on a newer machine.


Let me try that quickly on the jobs you fixed.

Thanks for taking care of those, Ignasi!

ap

Fwd: Jenkins build is back to normal : jclouds-aggregate-javadocs #1063

[Andrew Phillips]

Hi all

Quick FYI that the Javadocs from HEAD are building again:

http://jclouds-javadocs.elasticbeanstalk.com/

Have a good weekend, everyone!

ap

 Original Message 
Subject: Jenkins build is back to normal : jclouds-aggregate-javadocs 
#1063

Date: 2018-02-24 00:06
From: jenkins-no-re...@cloudbees.com
To: andr...@apache.org

See 

Re: jenkins CI for 2.1.x

[Andrew Phillips]

I'd like another pair of eyes to validate it.


Thanks for setting that up, Andrea!

Just FYI that I added the new 2.1.x builds to some of the views, and 
updated the groups settings so the publicly visible jobs match those in 
the "public" view.


On a different Jenkins-related note: does anyone know if the 
(non-public) "profitbricks-2.0.2" job is still needed?


Regards

ap

Re: Openstack Keystone v3 finally!

[Andrew Phillips]

A quick update on this: we're running the final tests before opening
the pull request.


Yeh!!

ap

Re: Skeleton page for Jan 2018 board report up

[Andrew Phillips]

> @demobox, all, please provide your comments as I'd like to send the report 
>today possibly
Some phrasing edits in 
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=74691908=7=6
 - the statements themselves should be essentially unchanged.
A possible suggestion for next time: shall we drop "supported" from the "A 
cloud agnostic library that enables developers to access a variety of supported 
cloud providers using one API." tagline? It seems a bit tautological since it 
would be difficult for the library to enable developer to access *unsupported* 
cloud providers?
Regards
ap

Skeleton page for Jan 2018 board report up

[Andrew Phillips]

Hi all

Just a quick FYI that I've put up the usual skeleton page for next 
month's board report:


https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+January+Board+Report+Draft

Please edit as necessary.

Hope it's been a fun and relaxing holiday break for those who've been 
able to take time off!


Regards

ap

Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1

[Andrew Phillips]

+1 to file an issue to properly track this.


https://issues.apache.org/jira/browse/JCLOUDS-1361

Do you know if with our current plan we could have some Windows build 
in CloudBees?


Based on 
https://go.cloudbees.com/docs/cloudbees-documentation/dev-at-cloud/#operating-system, 
I suspect the answer is "no" :-(


@abayer: any thoughts on that?

Regards

ap

Re: Please ping if gsoc2016-ivan branch is still needed

[Andrew Phillips]

It can be removed. His work was merged to master!


Done:

To https://andr...@git-wip-us.apache.org/repos/asf/jclouds.git
 - [deleted] gsoc2016-ivan

Thanks for clarifying, Ignasi!

ap

Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1

[Andrew Phillips]

However, I am unclear on why the test fails since the filesystem 
blobstore should convert user input /
to backend fs separator \ on Windows.  That is to say, code which runs 
on Linux and Windows *should*

behave identically, although in previous releases they did not.


PR to prevent the test failure here: 
https://github.com/jclouds/jclouds/pull/1162


I'm not sure this change is correct, given that (as Andrew G pointed 
out) the code is actually *not* expected to fail on Windows (and thus 
the test is expected to pass).


From a quick local test, this test was already failing in 2.0.2 (when it 
was first added [1]), so the original implementation may simply have 
been incomplete. Since we have't seen any related comments or issues, as 
far as I am aware, I'd agree that this is probably not a reason to stop 
the release.


Would it make sense to try to fix the underlying problem, or at least 
open a bug to track this, though?


Regards

ap

[1] 
https://github.com/jclouds/jclouds/commit/6452960c72a5f8247acae12481b94cdf9d8e4218#diff-9592ea1a2837c5f2cd419db6bde4fd5d

Please ping if gsoc2016-ivan branch is still needed

[Andrew Phillips]

Hi all

Is the "gsoc2016-ivan" branch [1] still needed? The last commit was in 
Aug 2016, and at this point it's 496 commits behind master.


Please ping if the branch is still required, otherwise I'll remove it 
over the weekend.


Thanks!

ap

[1] https://github.com/jclouds/jclouds/tree/gsoc2016-ivan

Re: [DISCUSS] Release Apache jclouds 2.0.3 RC1

[Andrew Phillips]

Please use this thread for discussion of issues uncovered in the RC,
questions you may have about the RC, etc.


The following test fails repeatedly for me on Windows:

Failed tests:
  
FilesystemStorageStrategyImplTest.testDeletingInvalidPathFileEndsNormally:695

Deleting an invalid path ended with an InvalidPathException.

Specifically, it's the "/" character in the test input "A/\0"; removing that works.


Would having an OS-specific test input seem like the correct solution? 
Or should the test be modified to expect a test failure on Windows?


Regards

ap

Re: archive legacy-jclouds repositories

[Andrew Phillips]

> Independently of this I would like to change all the READMEs to point
> to
> our new JIRA and GitHub URLs:
> https://github.com/jclouds/legacy-jclouds/pull/1584

Added a quick comment about that; +1 regarding the repository archiving, 
especially as that seems to be a reversible change, if for some reason we would 
want to do that.

Thanks for spotting this!

ap

Updated andrewp's code signing key expiration

[Andrew Phillips]

Hi all

Just a quick heads-up that I've extended the validity of my code signing 
key 892E5D10 [1, 2], which was due to expire. If you run into any key 
expiration errors in future for releases signed by that key, please 
refresh it locally be re-retrieving it from pgp.mit.edu.


Thanks!

ap

[1] http://pgp.mit.edu/pks/lookup?op=get=0x8474CCD0892E5D10
[2] https://www.apache.org/dist/jclouds/KEYS

Re: [jenkins-no-re...@cloudbees.com: Build failed in Jenkins: jclouds #3662]

[Andrew Phillips]

@gaul, could you have a look at the failures, as most of them appear
in the filesystem provider and S3 classes?


It looks as though BlobMetadata.getTier is returning null, even though 
according to the interface definition [1] it should be non-null?


Regards

ap

[1] 
https://github.com/jclouds/jclouds/blob/master/blobstore/src/main/java/org/jclouds/blobstore/domain/BlobMetadata.java#L49

Re: Common Scale Set API

[Andrew Phillips]

Hi Julio


Is this email address been monitored?


These emails have ended up in our moderation queue but should have been 
released successfully - at least, I've seen the previous one and your 
follow-up come through, and they also appear in the list history.


You may wish to subscribe to the list [1] to hopefully ensure emails get 
through directly in future.


Thanks for kicking off the Common Scale Set thread!

ap

[1] https://lists.apache.org/list.html?dev@jclouds.apache.org

Re: July board report due by Jul 12th

[Andrew Phillips]

I've added my comments. As usual, please fix/amend where needed.


Thanks, Ignasi! Some text edits at 
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=71013050=5=4.


@Ignasi: please check that I haven't accidentally changed the meaning of 
any of your comments.


Regards

ap

Re: [DISCUSS] Release Apache jclouds 2.0.2 RC1

[Andrew Phillips]

Done :)


Wow, that was instant - thanks, Ignasi!

ap

Re: [DISCUSS] Release Apache jclouds 2.0.2 RC1

[Andrew Phillips]

Created a fix for the azure failure below at


@Svet: given that this is still open and the release has gone through, 
would it make sense to add this as a Known Issue?


https://github.com/jclouds/jclouds-site/pull/198/files#r125906893

Regards

ap

July board report due by Jul 12th

[Andrew Phillips]

Hi all

Time for the next board report, due by July 12th. I've created a 
skeleton draft page at:


https://cwiki.apache.org/confluence/display/JCLOUDS/2017+-+July+Board+Report+Draft

Please add/amend as desired!

Regards

ap

Re: Time to release jclouds 2.0.2

[Andrew Phillips]

If there are no objections, I plan to start the release process this 
week.


Sounds good to me - thanks for volunteering to lead this again, Ignasi!

ap

Re: Adding async support for Jclouds library

[Andrew Phillips]

Hi Kishore

Andrew G. is travelling for most of June, as far as I understand, so 
will likely be a bit slower to respond. Thanks for your patience!


ap

On 2017-06-05 23:42, Battula Kishore wrote:

Hi Andrew,

Any update on this?

-- Thanks
-- Kishore










On 29/05/17, 1:06 PM, "Battula Kishore"  
wrote:



Hi Andrew,

Thanks andrew for the quick response. Here is the GitHub repo and 
instructions on how to run the tests 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkishore25kumar%2Fs3proxy-async-test-setup=02%7C01%7C%7C8969ed65c6a749aebfa608d4a66583cc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636316402308126519=0YESeCSlmChUOicpe2m9SYC1WaB7m%2B7hIB6o%2BTOp1Jo%3D=0. 
The READE.md also has the repo details of s3proxy as well as jclouds 
implementation. Hope this helps? Let me know if you need anything 
else?


In the mean time you review these results if you can let me know the 
design review process I can be prepared for that.


-- Thanks
-- Kishore









On 26/05/17, 12:40 PM, "Andrew Gaul"  wrote:

Kishore, these are promising results!  I reformatted the most 
important

rows which show a 2x improvement in throughput and latency:

10 10,000 Async Http Lib 209 282 48
10 10,000 OutputStream   392 542 25

Can you share the implementation and include instructions on how to
replicate these tests?

On Wed, May 24, 2017 at 05:50:52AM +, Battula Kishore wrote:

Hi,

This is Kishore who is working on async poc using mail 
id(kishore25ku...@gmail.com). I 
work at adobe and we wanted to implement async support for jclouds 
library and contribute it back.


From the last discussion I was asked to get the performance numbers 
for the two approaches.

Approach 1: Using Http Async Library
Approach 2: Using Outputstream

Test setup:

1.   Both the s3 proxy server and test runner are running in 
same Docker container in azure west-us region.


2.   Azure storage account is also residing in same west-us 
region.


3.   A bucket is prepopulated with 100,000 files, each file of 1 
MB size before test start.


4.   The test runner sends unique requests to s3proxy to 
download files.


Virtual Machine spec: CPU - 8 cores, Memory - 28 GB (Standard_D4 
Azure machine)


S3proxy is running with 1 jetty worker thread in all the scenarios. 
The payload size used is 1 MB file. Here are the performance 
numbers.

Test Runner Threads

Iteration Per thread

Approach

Avg response time (ms)

99%tile time (ms)

Throughput
(Requests / sec)

1

10,000

Async Http Lib

45

87

22

5

10,000

Async Http Lib

107

159

47

10

10,000

Async Http Lib

209

282

48

1

10,000

OutputStream

41

85

24

5

10,000

OutputStream

190

283

26

10

10,000

OutputStream

392

542

25


Summary: Under load Http Async Library approach is providing more 
throughput compared to Output stream approach.



Both the approaches improve performance. The output stream approach 
can be used along with Http Async library approach which is giving 
around (3-5 ms) improvement in latency.


Each approach is independent development. At this point I am keen to 
take up Http Async Library development.



-- Thanks
-- Kishore



--
Andrew Gaul
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgaul.org%2F=02%7C01%7C%7C8690ee3e00bc4e3da0e608d4a406565e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636313794511467457=XQ%2FshVjdqC3KiVEuyH6%2FJvmDN5DHBmS0kIBx98V89KY%3D=0

Re: Deprecate and remove the Azure Classic provider

[Andrew Phillips]

* Do you agree to deprecate and remove Azure Classic?
* If so, should we remove it in the next major (2.1.0) or wait for the
next one, 2.2.0?


Also +1 on removing this in 2.1.0 - perhaps send a heads-up out to the 
user list to see how many (if any) people are using it that might need 
more time to migrate?


Thanks for picking this up, Ignasi!

ap

Re: Apache jclouds needs your help

[Andrew Phillips]

I just wanted to say thanks for your quick and great support.


A big +1 to that - many thanks for helping out!

ap

Fwd: DEV@cloud planned maintenance

[Andrew Phillips]

FYI... 

ap 

 Original Message  

SUBJECT:
DEV@cloud planned maintenance

DATE:
2017-04-13 14:03

FROM:
"CloudBees, Inc." 

View this email in your browser [1] 

 [2] 

DEV@cloud Update  

Dear , 

On 24th April from 12am-6am UTC we will restart DEV@cloud customer
instances to apply changes critical to the stability and security of
your service.

During this window your instance will become temporarily unavailable as
it is restarted. You can receive real time notifications by visiting our
status page and subscribing. [3] 

As part of this maintenance window CloudBees is deprecating the
On-Premise Executor in favour of standard Jenkins SSH and JNLP agents.
For more information please see our migration guide [4]. As a
side-effect, customers using the Jenkins CLI are advised to update the
jenkins-cli.jar after the maintenance.  

As always if you experience any issues or have any questions please
don't hesitate to open a case [5] withour Customer Engagement team. 

Regards,

James G. Brown III
Sr. Director of Global Customer Success 

2001 Gateway Place, Suite 670W, San Jose, CA 95110, United States |
408-805-3552 

(c) CloudBees, Inc. 2010-2017 

Privacy Policy [6] | Terms of Service [7]  | U [7]nsubscribe [8] 

 [9]  [10]  [11]  [12]

 

Links:
--
[1]
http://join.cloudbees.com/webmail/272242/12643127/33b2d27c8d6bc054a8b5e02fe63abcae23b0b701f8dfe60dd215f0b03cbbcd91
[2] http://join.cloudbees.com/e/272242/2017-04-13/3s628/12643127
[3]
http://join.cloudbees.com/e/272242/incidents-bh61g878rnzl/3s62b/12643127
[4]
http://join.cloudbees.com/e/272242/e-Executors-to-standard-agents/3s62d/12643127
[5] http://join.cloudbees.com/e/272242/2017-04-13/3s62g/12643127
[6] http://join.cloudbees.com/e/272242/privacy-policy/3s62j/12643127
[7] http://join.cloudbees.com/e/272242/terms-service/3s62l/12643127
[8]
http://join.cloudbees.com/unsubscribe/u/272242/33b2d27c8d6bc054a8b5e02fe63abcae23b0b701f8dfe60dd215f0b03cbbcd91/12643127
[9] http://join.cloudbees.com/e/272242/CloudBees/3s62n/12643127
[10] http://join.cloudbees.com/e/272242/cloudbees/3s62q/12643127
[11] http://join.cloudbees.com/e/272242/company-cloudbees/3s62s/12643127
[12] http://join.cloudbees.com/e/272242/CloudbeesHive/3s62v/12643127

Re: April Board Report draft page

[Andrew Phillips]

Yes, it still needs to be improved :)


Ah, thanks for confirming, Ignasi! Tweaked that and made a couple of 
other minor changes:


https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=68719231=4=3

Regards

ap

Re: April Board Report draft page

[Andrew Phillips]

I elaborated the points a little bit, as this kind of format is the
preferred one by the board.


Thanks, Ignasi!

Is the "Cluster of activity in OpenStack Swift provider." 
sentence/bullet point still intended to be there? If so, we should 
probably phrase it in a similar "longhand" style?


Regards

ap

Re: April Board Report draft page

[Andrew Phillips]

Hi all

A quick reminder that this is due in just over a week...

Regards

ap

On 2017-03-15 16:18, Andrew Phillips wrote:

Hi all

In preparation for next month's board report, I've created the usual
draft page in the Wiki:

https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+April+Board+Report+Draft

Deadline looks like April 11th; please update as appropriate.

Thanks!

ap

Fwd: DEV@cloud planned maintenance

[Andrew Phillips]

FYI... 

ap 

 Original Message  

SUBJECT:
DEV@cloud planned maintenance

DATE:
2017-03-31 14:33

FROM:
"CloudBees, Inc." 

TO:
andr...@apache.org

View this email in your browser [1] 

 [2] 

DEV@cloud Planned Maintenance 

Dear DEV@Cloud user,  

 On 10th April from 12am-6am UTC we will restart DEV@cloud customer
instances to apply changes critical to the stability and security of
your service.

During this window your instance will become temporarily unavailable as
it is restarted. We do not expect individual instances to be impacted
for more than 45 minutes.

You can receive real time notifications by VISITING OUR STATUS PAGE AND
SUBSCRIBING [3]. 

As always if you experience any issues or have any questions please
don't hesitate to OPEN A CASE [4] with our Customer Engagement team. 

Best regards,

James G. Brown III
Sr. Director of Global Customer Success 

2001 Gateway Place, Suite 670W, San Jose, CA 95110, United States |
408-805-3552 

(c) CloudBees, Inc. 2010-2016 

Privacy Policy [5] | Terms of Service [6]  | U [6]nsubscribe [7] 

 [8]  [9]  [10]  [11]

 

Links:
--
[1]
http://join.cloudbees.com/webmail/272242/5067/33b2d27c8d6bc054a8b5e02fe63abcae23b0b701f8dfe60dd215f0b03cbbcd91
[2] http://join.cloudbees.com/e/272242/2017-03-31/3qy98/5067
[3] http://join.cloudbees.com/e/272242/2017-03-31/3qy9b/5067
[4] http://join.cloudbees.com/e/272242/2017-03-31/3qy9d/5067
[5] http://join.cloudbees.com/e/272242/privacy-policy/3qy9g/5067
[6] http://join.cloudbees.com/e/272242/terms-service/3qy9j/5067
[7]
http://join.cloudbees.com/unsubscribe/u/272242/33b2d27c8d6bc054a8b5e02fe63abcae23b0b701f8dfe60dd215f0b03cbbcd91/5067
[8] http://join.cloudbees.com/e/272242/CloudBees/3qy9l/5067
[9] http://join.cloudbees.com/e/272242/cloudbees/3qy9n/5067
[10] http://join.cloudbees.com/e/272242/company-cloudbees/3qy9q/5067
[11] http://join.cloudbees.com/e/272242/CloudbeesHive/3qy9s/5067