[foreman-dev] vmware html5 console support

[Michael Eklund]

I am interested in support for the html5 console for vmware in place of the 
vnc console.  I have a proof of concept of sorts by overwriting the 
vm_console call in compute_resources_vms_helper.rb.  The jist of it is a 
url that looks like this:

 html5_link = 
"https://#{vcenter_url}:9443/vsphere-client/webconsole.html?vmId=#{vm.mo_ref}=#{vm.name}=#{server_guid}=en_US=#{vcenter_url}:443=cst-VCT=#{cert_sha1_thumbprint};

The vm variables are all natively supported.  I am not sure if the server 
guid and server certificate sha1 thumbprint are collected.  

This should be supported in vcenter 6+, possibly 5.5+.  I would be happy to 
work on a better implementation then my hack, if there is interest and I 
could get some guidance on what might be the best way to implement this.

Thanks,

Mike E.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] redmine issues for failing forklift devel?

[Tom McKay]

Are there specific redmine issues tracking the failing forklift devel
failure? This is impacting closing out work for releases.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [foreman-dev] Nominating Daniel Lobato for commiter to release related tasks

[Daniel Lobato Garcia]

On 04/26, Dominic Cleal wrote:
> On 25/04/17 12:45, Marek Hulán wrote:
> > On úterý 25. dubna 2017 9:19:40 CEST Dominic Cleal wrote:
> >> On 24/04/17 12:59, Marek Hulán wrote:
> >>> based on our handbook [1]. I'd like to nominate Daniel for commit access
> >>> to
> >>>
> >>> the following repositories:
> >>>  - foreman-infra
> >>>  - foreman-installer
> >>>  - foreman-packaging ( to branch and cherry-pick to the release branch )
> >>>
> >>> Daniel contributes to the project for a long time, also in this area
> >>> [2][3][4] and always has only the best intentions. He worked on 1.15 RC1
> >>> and I think there's no reason why he shouldn't have access to places
> >>> which are needed to update during the release process.
> >> These repos all have active maintainers and so making a pull request (as
> >> Daniel's done on two of them) is a better way to make changes. I don't
> >> think commit access is necessary to submit updates to these repos and
> >> shouldn't be encouraged here for Foreman releases.
> > I'm happy to hear that there are active maintainers. I'm not sure whether 
> > you
> > suggest that it is the reason why commit access should not be granted? I 
> > think
> > the more active committers the better. Doing this through PR is fine and as
> > you say, it can find issues. But if other devs send PRs, I think it makes
> > sense if Daniel can merge them. Commit access is also required to create
> > branches and tags which I don't think needs any form of reviewing.
> >
> > I'm sorry if it seemed like I'm encouraging pushing commits directly without
> > PR during release process. That was not subject of this nomination.
>
> OK, sorry, that's what I thought you were suggesting. In that case, I
> don't think Daniel's had much involvement with the foreman-infra or
> foreman-installer projects to warrant commit access. He's opened a lot
> of PRs against foreman-packaging, but I'd want to see fewer common
> errors in recent PRs before seconding him for commit access.

It's true I've made sloppy mistakes on -packaging (especially recently).
I'm happy to pay more attention on future PRs to avoid having other
people (mostly you.. though :/) have to double-check carefully my PRs.

For -infra I don't really need commit access, however you're the only
active maintainer, which is not an ideal situation in case something
needs to be done during holidays etc..

About -installer, I don't mean to update anything there, except for
tagging stuff for the releases. I'm not sure if there's a way to give
permission to just branch and tag but not commit to the develop branch.

>
> --
> Dominic Cleal
> domi...@cleal.org
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

[foreman-dev] hammer-cli and hammer-cli-foreman 0.10.2 released

[Tomas Strachota]

New minor versions of hammer-cli and hammer-cli-foreman were released.
They contain fixes around fetching server CA certs and retry mechanism
when session expires.

This should go to the next foreman 1.15 RC.

PR into rpm packaging is open at:
https://github.com/theforeman/foreman-packaging/pull/1638

Cheers
Tomas

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] hammer-cli, -foreman version numbers on master

[Tomas Strachota]

Done, versions in both repos bumped to 0.11-develop and strings
extracted in the master.

Thanks
T.

On Fri, May 5, 2017 at 3:25 PM, Dominic Cleal  wrote:
> On 05/05/17 14:21, Tomas Strachota wrote:
>> Is it enough just to bump the version to 0.11-develop or do I need to
>> do whole new release?
>
> Bumping/changing the version number is fine, thanks.
>
> --
> Dominic Cleal
> domi...@cleal.org
>
> --
> You received this message because you are subscribed to the Google Groups 
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] hammer-cli, -foreman version numbers on master

[Dominic Cleal]

On 05/05/17 14:21, Tomas Strachota wrote:
> Is it enough just to bump the version to 0.11-develop or do I need to
> do whole new release?

Bumping/changing the version number is fine, thanks.

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] hammer-cli, -foreman version numbers on master

[Tomas Strachota]

Is it enough just to bump the version to 0.11-develop or do I need to
do whole new release?

T.

On Fri, May 5, 2017 at 11:11 AM, Dominic Cleal  wrote:
> The version numbers on hammer-cli and hammer-cli-foreman's master
> branches are currently behind the latest release (from the 0.10-stable
> branch) which is causing a small issue with RPM packaging tests -
> packages are built with the .1 spec files, but the version numbers are
> set to .0.
>
> Martin or Tomas, could you please increment the version on master to
> either match or exceed the latest released version? i.e. 0.10.1, .2, or
> 0.11.0
>
> There's also a change to the POT file on the 0.10-stable branches which
> won't be picked up by Transifex which uses master. This should be
> changed on master too, or Transifex needs reconfiguring to use the
> stable branch.
>
> Cheers,
>
> --
> Dominic Cleal
> domi...@cleal.org
>
> --
> You received this message because you are subscribed to the Google Groups 
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.