Re: [foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT]

[Bernhard Suttner]

Hi, 




Are you interested in having a demo about the foreman_scc_manager plugin which 
we have developed at ATIX? 




Plugin can be found here: 

https://github.com/ATIX-AG/foreman_scc_manager 





Short discription: 
Foreman plugin to sync SUSE Customer Center products and repositories into 
Katello 




Best regards 
Bernhard 

--- 
ATIX - The Linux & Open Source Company 
www.atix.de 


Von: "greg sutcliffe"  
An: foreman-dev@googlegroups.com 
Gesendet: Donnerstag, 25. Mai 2017 16:35:35 
Betreff: [foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm 
[GMT] 

Hi all 

Demo time! As always, have a think for items which have been completed since 
the last demo on 2017-05-11. There is a query that will show you items 
completed (i.e. marked as closed) since the last demo [2]. Please add demo 
items following the instructions on the agenda page [3]. 

If you can't be present but have something to show, add it to the agenda and 
let me know - I'll be happy to talk about the feature in your absence. Please 
do leave me enough time to familiarize myself with the content though :) 

[1] https://www.youtube.com/watch?v=_OrYpestGQc 
[2] http://tinyurl.com/lhwqdyh 
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information 

Cheers! 
-- 
Greg 
IRC: gwmngilfen 

-- 
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] Weekly Dev/Design Meeting: Discovered Hosts

[Roxanne Hoover]

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
>>
>>
>>- 
>>
>>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.
>>
>>
>>
>>
>>
>>- 
>>
>>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.
>>
>>
>>
>>- 
>>
>>Warning be placed at the top. 
>>
>>
>>
>>
>>- 
>>
>>Discovered Hosts empty state should be similar to empty state of 
>>Hosts.
>>
>> -- 
>> 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] Migration to Copr POC

[Lukas Zapletal]

Hello Justin!

> 1.  Currently we rebuild candlepin srpms in our koji, sign them, and publish
> the srpm and rpm
>
> Should we continue doing this? (in which case we likely need to setup a copr
> build root for it).

So you want to create Copr repositories in @theforeman Copr group for
that, Candlepin package would perhaps be in katello repository, or you
can create a separate one if you prefer to.

> 2. Currently for pulp, we pull in the pulp projects build from our koji into
> our tags, and publish in our repositories (signed by our key).

I believe Copr does not support "retagging" releases, Mirek can you
suggest the best workflow in this case? You will need to import
existing packages there, rebuild in the worst case.

Copr automatically signs all builds by default with it's own internal
key (which cannot be changed or uploaded - it's built in). This is
acceptable for nightly builds, but for regular releases we will need
to download all packages and sign them by hand anyway. That's the
workflow we plan for Foreman core.

> I think we likely should start pointing to their major release repos
> instead.  There is a chance that there could be some breaking change, but i
> feel like their z-stream builds over the past year have been increasingly
> stable and more often our users are requesting that we update to the latest
> pulp zstream before we are able to.

The plan is to keep Koji running for longer period of time, we are
thinking one year. So Pulp 2 would be kept in Koji as well as older
Katello (Candlepin) and Foreman versions. So we will only change
workflow in future upcoming release and keep the old one for released
packages.

> 3.  can we start building katello in the foreman 'build root' in copr?

Mirek, please confirm, but the suggested setup would be a katello copr
repository with foreman build root, so your packages would end up in
your own repository

LZ

-- 
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: Why does foreman support only one provisioning template per operating system?

[nokrite]

Hello Greg,

finally, i solve the problem. It seems a lower/uppercase conflict.

Thank you for your posting. This helps me a lot.

Best Regards

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