Re: [foreman-dev] Weekly Dev/Design Meeting: Discovered Hosts

[rahul bajaj]

On Friday, May 26, 2017 at 6:15:55 PM UTC+5:30, Roxanne Hoover wrote:
>
> Thanks! If additional work is needed from me including mockups, etc. 
> please do not hesitate to reach out!
>
> On Friday, May 26, 2017 at 6:58:28 AM UTC-4, Lukas Zapletal wrote:
>>
>> Thanks Roxanne,
>>
>> I've created a tracking ticket for the changes: 
>> http://projects.theforeman.org/issues/19681
>>
>> LZ
>>
>> On Thu, May 25, 2017 at 9:32 PM, Roxanne Hoover  
>> wrote:
>>
>>>
>>> https://docs.google.com/document/d/1BNxtczgB2_C6-rzdBwP7Mq3bwbUK7J6__qZe_EGGjE4/edit
>>>
>>>
>>> Discovered Hosts 
>>>
>>> Presented by Izap
>>>
>>>
>>>
>>>
>>>- 
>>>
>>>Icon use and color does not comply with PatternFly or with other 
>>>uses in the application
>>>- 
>>>
>>>Org/Location is not tracking the context selected by the user for 
>>>Org/Location
>>>
>>>
Hello Roxanne,

Can you please mention which icons are you talking about here ? 
 

>
>>>- 
>>>
>>>Reboot All, Auto Provision All should be added to Select Action 
>>>button
>>>
>>>
>>>  
>>>
>>
>>>
>>>
>>>- 
>>>
>>>Redundant info on the Highlight -  IP address, maybe change to 
>>>Primary IP
>>>- 
>>>
>>>Expand All button should be grouped with accordion, not with actions.
>>>- 
>>>
>>>Remove Back button, implement bread crumb.
>>>- 
>>>
>>>Change Delete from Red to Grey
>>>- 
>>>
>>>Move Highlights next to Interfaces with the Accordion below both of 
>>>those that can take up the entire width of the page reducing truncation 
>>> of 
>>>information.
>>>
>>>
can you please provide me a example of bread crumb that would be valid here 
?
Should it be like : Hosts / Discovered Hosts / user  ?  

>
>>>
>>>- 
>>>
>>>Priority counter should use patternfly touchspin, 
>>>http://www.patternfly.org/pattern-library/widgets/#bootstrap-touchspin
>>>
>>>
>>>
>>>
>>>- 
>>>
>>>This combo select button users find confusing and are prone to click 
>>>error… just a note that a long term strategy should be identified to fix 
>>>it. I’m specifically referring to buttons that utilize the small chevron 
>>>box on the right as the drop down action.
>>>
>>>
>>>
>>>- 
>>>
>>>Style of modal doesn’t follow PatternFly (
>>>http://www.patternfly.org/pattern-library/widgets/#modal)
>>>- 
>>>
>>>Change “Close Button” to “Cancel” 
>>>- 
>>>
>>>“Create Host” - name is inaccurate, possibly change to “Customize”
>>>- 
>>>
>>>Determine which button is more common, “Quick Create” or “Create 
>>>Host” and color the more common action blue.
>>>
>>>
>>> Fixed this : https://github.com/theforeman/foreman_discovery/pull/357 

>
>>>- 
>>>
>>>Warning be placed at the top. 
>>>
>>>
Fixed this : https://github.com/theforeman/foreman_discovery/pull/357 

>
>>>
>>>
>>>- 
>>>
>>>Discovered Hosts empty state should be similar to empty state of 
>>>Hosts.
>>>
>>>
On it :)

Thanks, 
Rahul Bajaj.

> -- 
>>> 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...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Later,
>>   Lukas @lzap Zapletal
>>
>

-- 
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] Proposal: Update Pulp to 2.13.2 in Katello 3.4

[Tom McKay]

+1 There are a number of fixes in pulp-2.13 related to syncing container
images from registries. The schema-2 will perhaps cause some visual oddness
in UI but not blocker to functionality. I would suggest raising the
priority of those issues for fixing by katello-3.15.

On Fri, Jun 30, 2017 at 9:11 AM, Justin Sherrill 
wrote:

> +1, there is a nasty bug that prevents the syncing of some yum repos which
> sadly isn't being backported.  That seems severe enough to warrant pulling
> it in IMHO.
>
> Justin
>
> On 06/28/2017 08:36 PM, Eric D Helms wrote:
>
> Devs,
>
> I am proposing to update Katello 3.4 to Pulp 2.13.2 in order to pull in a
> number of fixes that are affecting users. These updates would move us to
> the most recent stable release of Pulp and prevent users from having to do
> work arounds to fix repositories that occasionally break.
>
> One question is around changes to how Docker Schema V2 are handled and are
> addressed by the open PR [1]. The inclination is to include that change
> along with the update.
>
> If anyone has any objects, questions or approval please speak up. This
> would most likely be done as a stand-alone release update to limit the
> amount of change.
>
> [1] https://github.com/Katello/katello/pull/6775
>
> --
> Eric D. Helms
> Red Hat Engineering
> --
> 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.
>

-- 
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] Proposal: Update Pulp to 2.13.2 in Katello 3.4

[Justin Sherrill]

+1, there is a nasty bug that prevents the syncing of some yum repos 
which sadly isn't being backported.  That seems severe enough to warrant 
pulling it in IMHO.


Justin


On 06/28/2017 08:36 PM, Eric D Helms wrote:

Devs,

I am proposing to update Katello 3.4 to Pulp 2.13.2 in order to pull 
in a number of fixes that are affecting users. These updates would 
move us to the most recent stable release of Pulp and prevent users 
from having to do work arounds to fix repositories that occasionally 
break.


One question is around changes to how Docker Schema V2 are handled and 
are addressed by the open PR [1]. The inclination is to include that 
change along with the update.


If anyone has any objects, questions or approval please speak up. This 
would most likely be done as a stand-alone release update to limit the 
amount of change.


[1] https://github.com/Katello/katello/pull/6775

--
Eric D. Helms
Red Hat Engineering
--
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.

[foreman-dev] Re: Plugins configuration managment platform

[Fairouz el ouazi]

Hi , it's me again im really sorry for asking a lot of question but when 
take a look to the documetation i didn't get a clear idea about the real 
job of smart proxy chef plugin and why on chef we have a client plugin  and 
on salt we don't have it ?? and if my platform is not agent less would it 
be necessary to have 3 plugin one on foreman and other one on smart proxy 
foreman and the third on my  iot devices ?
Le mercredi 28 juin 2017 11:50:40 UTC+2, Fairouz el ouazi a écrit :
>
> Hi everyone ,
>
>  I'm a beginner in using foreman ,So before in take the adventure i 
> want to know if the fact that it exists a plugin for managing chef is there 
> any chance to develop a new one that will manage my own platform  X 
> (PLatform that manage IOT  devices ) . So  at place of having chef client i 
> will have foreman dealing with the devices of my X platform . ???
>
> I really need your help or some ideas or if anyone has face the same 
> uses cases ? 
>
>

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