FWIW, we know that several of the changes in the (recently committed)
        METRON-634 Mpack bug fixes and improvements, not impacting Ambari 
database (PR#532)
are necessary for a smooth install on Centos7.  These changes are for the 
manual install wizard, but all the non-“description” changes would be needed in 
the blueprint also.  And for that matter the “description” changes may be 
desirable for post-install config management.

Thanks,
--Matt

On 4/25/17, 10:29 AM, "Michael Miklavcic" <[email protected]> wrote:

    We didn't come up with another approach Otto. I closed the PR at the time
    bc I didn't think we wanted to break with Centos 6 yet, and my PR probably
    would have done so. Can you elaborate on "prior capability wrt centos 6.x
    work again" a bit?
    
    On Apr 25, 2017 10:59 AM, "Otto Fowler" <[email protected]> wrote:
    
    > Also, I can’t find any list discussion of the issue or other approaches.
    >
    >
    > On April 25, 2017 at 12:48:46, Otto Fowler ([email protected])
    > wrote:
    >
    > What I am looking for is the prior capability wrt centos 6.x work again (
    > which I think my
    > pr fixing the docker in docker issue would do ), and have it extended to
    > work with 7.x.
    >
    > I don’t think re-writing all the stuff that is in metron roles is very
    > attractive.
    >
    >
    > On April 25, 2017 at 12:10:47, David Lyle ([email protected]) wrote:
    >
    > So, the current Ansible deployment actually does use blueprints. It
    > constructs them from one of small_cluster.yml or single_node_vm.yml using
    > the ambari_custer_state module.
    >
    > Ambari blueprints [1] and the Ambari Install Wizard are actually two
    > separate things that are only related because both are available via
    > Ambari.
    >
    > Currently, you should be able to create a blueprint and instantiate a
    > cluster on Centos7 without using Ansible at all, though if you wished to,
    > you could realize your blueprint in the same way that small_cluster and
    > single_node_vm do, or alternatively create some Ansible roles to make the
    > REST calls that Ambari requires to stand up a cluster.
    >
    > -D...
    >
    >
    > [1] https://cwiki.apache.org/confluence/display/AMBARI/Blueprints
    >
    > On Tue, Apr 25, 2017 at 11:35 AM, Otto Fowler <[email protected]>
    > wrote:
    >
    > > Let me clarify, that this is support for automated blueprint deployment
    > > with ansible, not the ambari wizard.
    > >
    > >
    > >
    > > On April 25, 2017 at 11:31:37, [email protected] ([email protected])
    > wrote:
    > >
    > > Just tagging on here to indicate my interest in this - in order to have
    > > someone other than me manage the OSs in my Metron cluster, I must run on
    > > RHEL 7. I assume that will be common across many enterprises.
    > > Semi-recentlyI took a stab at CentOS 7 support but it was a bit of a
    > rough
    > > go and I dropped it down on my priority list.
    > >
    > > Jon
    > >
    > > On Tue, Apr 25, 2017 at 11:28 AM Otto Fowler <[email protected]>
    > > wrote:
    > >
    > > > https://issues.apache.org/jira/browse/METRON-153
    > > >
    > > > What is the other approach that is mentioned here? Was it implemented?
    > > > The ansible build still does not support this and I was thinking of
    > > looking
    > > > at it.
    > > >
    > > --
    > >
    > > Jon
    > >
    >
    


Reply via email to