June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-450: -------------------------------------------- You know I am quick! I think for this release this would be ok. It would not be big change. But even right now I could change the files from one folder to another, no problem. I consider also that could be maybe better to have the overlord.keystore in the commons profile. Even if we place the file there, it would not affect rtgov, as you are not using that file. > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-450: -------------------------------------------- Noo, I decoupled the fuse ant script just to call to the generate-keystore target. > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-450: ---------------------------------- Another question - is the commons installer going to setup the 'admin' user, with the password entered by the user? > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-450: ---------------------------------- Hi David A bit premature :) we haven't got agreement on where the keystore should be placed. That was only my opinion - we need [~ewittmann] to give his thoughts. I've also been considering this more, and wondering whether (even though not used currently) it may be better for the keystore to be in commons - and change where sramp obtains the keystore information from - to be in a commons property file. > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-450: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/426, https://github.com/Governance/overlord-commons/pull/75 > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-450: -------------------------------------------- Ok, gary, Going to do the following: - Place the keystore in the s-ramp-profile. Set the sramp-ui.properties with the default keystore references and properties. About the note you mentioned at the end of your message, I do not think it would affect that different overlord-subprojects are being installed sharing overlord-commons. We need to think fuse fabric profiles, like adding features to the container. If we add the overlord-commons-profile features to the same container multiple times, the result is gonna be the same, because the features related the profile would be only added once. > S-ramp installer && S-ramp-distro add fabric as a new target > ------------------------------------------------------------ > > Key: SRAMP-450 > URL: https://issues.jboss.org/browse/SRAMP-450 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly. > The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation. > The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-487) The JAR/ZIP file geronimo-jta_1.0.1B_spec-1.0.1.jar seems corrupted, error

by Gary Brown (JIRA)

Gary Brown created RTGOV-487: -------------------------------- Summary: The JAR/ZIP file geronimo-jta_1.0.1B_spec-1.0.1.jar seems corrupted, error Key: RTGOV-487 URL: https://issues.jboss.org/browse/RTGOV-487 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Error when building in hudson: {noformat} [ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:2.3.7:bundle (default-bundle) on project rtgov-switchyard: Error calculating classpath for project MavenProject: org.overlord.rtgov.integration:rtgov-switchyard:2.0.0-SNAPSHOT @ /qa/hudson_ws/workspace/overlord-rtgov/sources/integration/switchyard/pom.xml: The JAR/ZIP file (/qa/hudson_ws/workspace/overlord-rtgov/m2-repository/org/apache/geronimo/specs/geronimo-jta_1.0.1B_spec/1.0.1/geronimo-jta_1.0.1B_spec-1.0.1.jar) seems corrupted, error: error in opening zip file -> [Help 1] {noformat} Full log: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/overlord-rtgov/19/co... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-472) Commons httpclient 3.1 vulnerability detected

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-472?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-472. ------------------------------ Resolution: Done > Commons httpclient 3.1 vulnerability detected > --------------------------------------------- > > Key: RTGOV-472 > URL: https://issues.jboss.org/browse/RTGOV-472 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > rtgov-switchyard and karaf/features modules are reporting: > {noformat} > [WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783] > [WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message: > +=======================+ > |VULNERABILITY DETECTED!| > +=======================+ > For more information visit: > - https://access.redhat.com/security/cve/CVE-2012-5783 > {noformat} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-472) Commons httpclient 3.1 vulnerability detected

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-472?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-472: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/105 > Commons httpclient 3.1 vulnerability detected > --------------------------------------------- > > Key: RTGOV-472 > URL: https://issues.jboss.org/browse/RTGOV-472 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > rtgov-switchyard and karaf/features modules are reporting: > {noformat} > [WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783] > [WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message: > +=======================+ > |VULNERABILITY DETECTED!| > +=======================+ > For more information visit: > - https://access.redhat.com/security/cve/CVE-2012-5783 > {noformat} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-486) Align deployment targets with other overlord sub-projects

by Gary Brown (JIRA)

Gary Brown created RTGOV-486: -------------------------------- Summary: Align deployment targets with other overlord sub-projects Key: RTGOV-486 URL: https://issues.jboss.org/browse/RTGOV-486 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Change deployment targets to be consistent with other overlord sub-projects. For example, instead of jbossas, it should be eap6 (or eap61/63 if split required), and fuse61 instead of karaf - although support for Karaf will also be required. As part of this change, change the deployment approach to use ant script at top level, instead of maven - again for consistency with sramp/dtgov. Quickstarts could still use maven, unless deployment across targets is more consistent with ant. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014