-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dmitri,
Make sure you are using https. I've been bitten by just using http before. Josh On Wednesday, January 28, 2015 3:42:55 PM Dmitri Chebotarov wrote: > Hi Aaron > > I'm having troubles committing updated version of the one.pm module to > svn.apache.org. For whatever reason svn.apache.org doesn't like my > credentials for 'svn ci' command, but svn -co --username <> --password <> > is OK. > > Also it looks like svn.apache.org has a firewall policy which blocks my IP > address after few (3?) un-successful attempts to 'svn ci'. > > I've uploaded latest 'one.pm' to Jira's VCL-722 and will try to commit again > later - hopefully firewall block expires in few hours... > > > -- > Thank you, > > Dmitri Chebotarov > VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & > Messaging 223 Aquia Building, Ffx, MSN: 1B5 > Phone: (703) 993-6175 | Fax: (703) 993-3404 > > > On Jan 22, 2015, at 10:10 , Aaron Peeler <[email protected]> wrote: > > > > Hi Dmitri, > > > > Have you had a chance to do this yet and also test it against the > > trunk code? We are hoping to build the release candidate next > > week and would like to include this. > > > > In addition to your updated code, the vcl.sql and update-vcl.sql files > > will need to include the schema entries for the provisioning and > > module references. > > > > Thanks, > > Aaron > > > > On Fri, Jan 16, 2015 at 12:11 PM, Aaron Peeler <[email protected]> wrote: > >> Hi Dmitri, > >> > >> Have you had a chance to do this yet and also test it against the > >> trunk code? We are hoping to build the release candidate in the next > >> week or so and would like to include this. > >> > >> In addition to your updated code, the vcl.sql and update-vcl.sql files > >> will need to include the schema entries for the provisioning and > >> module references. > >> > >> Thanks, > >> Aaron > >> > >> On Fri, Dec 19, 2014 at 10:24 AM, Dmitri Chebotarov <[email protected]> wrote: > >>> Hi, > >>> > >>> I will upload updated code and documentation. Can also rename it to > >>> OpenNebula.pm. I've been running it since 2013 with few changes in our > >>> VCL environment. > >>> > >>> > >>> -- > >>> Thank you, > >>> > >>> Dmitri Chebotarov > >>> VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & > >>> Messaging 223 Aquia Building, Ffx, MSN: 1B5 > >>> Phone: (703) 993-6175 | Fax: (703) 993-3404 > >>> > >>>> On Dec 19, 2014, at 10:10 , Andy Kurth <[email protected]> wrote: > >>>> > >>>> one.pm > >>>> Dmitry worked on this in 2013. What is the status? Is there any > >>>> documentation? Is there any objection to renaming it OpenNebula.pm? > >>>> > >>>> esx.pm, esx.README > >>>> This module hasn't really been updated since 2009 other than minor > >>>> changes > >>>> made to all provisioning modules such as changing the version number. > >>>> I > >>>> don't believe it provides any functionality not provided by VMware.pm. > >>>> It > >>>> also causes confusion when someone inadvertently uses it instead of > >>>> VMware.pm. I propose removing it. Agree? > >>>> > >>>> esxthin.pm, esxthin.README > >>>> Again, this module was developed around the same time as esx.pm and > >>>> hasn't > >>>> been updated. It only works with certain NetApp hardware. I have no > >>>> way > >>>> to test it. > >>>> > >>>> Thanks, > >>>> Andy > >> > >> -- > >> Aaron Peeler > >> Program Manager > >> Virtual Computing Lab > >> NC State University > >> > >> All electronic mail messages in connection with State business which > >> are sent to or received by this account are subject to the NC Public > >> Records Law and may be disclosed to third parties. - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTJBlEACgkQV/LQcNdtPQMCPACfYcXXuJ5E2EXms7AAazyjNWI9 I18An1rs4cFwqS30o0YCaSX4ub36r+9x =qzuA -----END PGP SIGNATURE-----
