> +
> + org.apache.jclouds.karaf.bundles
> + jsch-agentproxy-jsch
> + jclouds :: Karaf :: JSCH Agentproxy Shaded Bundle
> + bundle
> +
> +
> +
> + org.apache.servicemix.bundles
> +
> org.apache.servicemix.bundles.jsch-agentproxy-jsch
> + ${jsch.agentproxy.bundle.version}
> +${import.packages}
> +
> +
> +
> +
> +org.apache.maven.plugins
> +maven-shade-plugin
> +2.4.3
> +
> +
> +package
> +
> + shade
> +
> +
> +
Ignasi Barrera created JCLOUDS-1172:
---
Summary: Script engines are not loaded in the interactive shell
Key: JCLOUDS-1172
URL: https://issues.apache.org/jira/browse/JCLOUDS-1172
Project: jclouds
Removed the offending commit that screwed up the poms and changed the parent of
the bundles one. Also moved the engine fix to
https://github.com/jclouds/jclouds-karaf/pull/78
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468829#comment-15468829
]
Ignasi Barrera commented on JCLOUDS-1172:
-
Well, the problem is not Groovy itself. It fails to
> +${import.packages}
> +
> +
> +
> +
> +org.apache.maven.plugins
> +maven-shade-plugin
> +2.4.3
> +
> +
> +package
> +
> + shade
> +
> +
> +
> @@ -37,7 +37,7 @@
>
>
>
> -2.0.0-SNAPSHOT
> +2.0.0-SNAPSHOT
Discard this change
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> +
> + public abstract String name();
> +
> + @SerializedNames({"id", "name"})
> + public static Server create(String id, String name) {
> + return new AutoValue_PrivateNetwork_Server(id, name);
> + }
> +
> + @AutoValue
> + public abstract static class
> + * the License. You may obtain a copy of the License at
> + *
> + * http://www.apache.org/licenses/LICENSE-2.0
> + *
> + * Unless required by applicable law or agreed to in writing, software
> + * distributed under the License is distributed on an "AS IS" BASIS,
> + * WITHOUT WARRANTIES OR
> The problem is that the scriptEngine is not loaded and is always null when
> running in the interactive shell, which results in silently printing null
> values when a NPE occurs.
Which value is passed in for the `engine` parameter? From your explanation and
what I can see in the code, the
> + final Predicate predicate = DockerComputeServiceAdapter
> +
> .createPredicateMatchingRepoTags("docker.io/kwart/alpine-ext:3.3-ssh");
> + assertFalse(predicate.apply(IMAGE_REPO_TAGS_MULTI));
> + assertFalse(predicate.apply(IMAGE_REPO_TAGS_EMPTY));
> +
Thanks @alibazlamit! Take care of reformatting the code to use 3 space
indentation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/315#issuecomment-244946602
> + assertNodeAvailable(currentServer);
> + currentPrivateNetwork =
> privateNetworkApi().create(PrivateNetwork.CreatePrivateNetwork.builder()
> + .name("jclouds privatenetwork")
> + .networkAddress("192.168.1.0")
> + .subnetMask("255.255.255.0")
>
> + public void testList() {
> + privateNetworks = privateNetworkApi().list();
> +
> + Assert.assertTrue(privateNetworks.size() > 0);
> + }
> +
> + @Test(dependsOnMethods = "testList")
> + public void testListWithOption() {
> + GenericQueryOptions options = new
> +
> + PrivateNetwork updateResult =
> privateNetworkApi().attachServer(currentPrivateNetwork.id(),
> PrivateNetwork.Server.CreateServer.create(servers));
> +
> + assertNotNull(updateResult);
> +
> + }
> +
> + @Test(dependsOnMethods = "testAttachServer")
> + public void
> I've also copied the classes mentioned here but that didn't work...
Just to confirm: you followed the instructions in that blog post and replaced
```
private final ScriptEngineManager scriptEngineFactory = new
ScriptEngineManager();
```
with
```
private final ScriptEngineManager
The question I would have at this point is whether this ever worked? I'd be
surprised if it was broken all the way from the time it was implemented. So I
wonder what has changed (on the Felix side?) to break this?
--
You are receiving this because you are subscribed to this thread.
Reply to
We are not passing any value. The [default
configuration](https://github.com/jclouds/jclouds-karaf/blob/master/feature/src/main/resources/shell.cfg)
does not set the engine value, so "groovy" was used (which seems to be the
[right
> @@ -23,6 +23,7 @@ limitations under the License.
> chef
> org.apache.jclouds.karaf
> 2.0.0-SNAPSHOT
> +../..
See comment below
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> @@ -23,6 +23,7 @@ limitations under the License.
> chef
> org.apache.jclouds.karaf
> 2.0.0-SNAPSHOT
> +../..
See comment below
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> @@ -21,6 +21,7 @@ limitations under the License.
> jclouds-karaf
> org.apache.jclouds
> 2.0.0-SNAPSHOT
> +..
Isn't that the default value?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> +http://www.apache.org/licenses/LICENSE-2.0
> +
> +Unless required by applicable law or agreed to in writing, software
> +distributed under the License is distributed on an "AS IS" BASIS,
> +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> +See the License for the
> @@ -23,6 +23,7 @@ limitations under the License.
> chef
> org.apache.jclouds.karaf
> 2.0.0-SNAPSHOT
> +../..
See comment below
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> @@ -23,6 +23,7 @@ limitations under the License.
> chef
> org.apache.jclouds.karaf
> 2.0.0-SNAPSHOT
> +../..
I don't think this is correct - the `chef` artifact is indeed one level up
--
You are receiving this because you are subscribed to this thread.
Reply to this email
@nacx Suggestion: break out the "fix output" issue out into a different JIRA
issue and PR? I think that's a slightly different discussion from the bundle
fix that this PR is about?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
> +http://www.apache.org/licenses/LICENSE-2.0
> +
> +Unless required by applicable law or agreed to in writing, software
> +distributed under the License is distributed on an "AS IS" BASIS,
> +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> +See the License for the
[
https://issues.apache.org/jira/browse/JCLOUDS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468807#comment-15468807
]
Andrew Gaul commented on JCLOUDS-1172:
--
Our use of Groovy is overkill for this formatting feature.
@nacx pushed 1 commit.
5f4d9d1 Fixed parent pom
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/77/files/228233239da796ee8c8b00692923fe57b3b47e22..5f4d9d15ede060019c0170ad476b79a45c8819a4
https://issues.apache.org/jira/browse/JCLOUDS-1172
Force the use of the default Groovy engine if the script engine factory can't
load any scripting engine. See
https://github.com/jclouds/jclouds-karaf/pull/77#issuecomment-244901813 for
more details.
You can view, comment on, or merge this
@nacx pushed 2 commits.
9c7d134 Addressed review comments
fc62962 Explicitly fallback to the Groocy scripting engine
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@demobox Addressed the review comments.
I've also been able to fix the display issue, but I'm pretty sure it is not the
best solution. The problem is that the
>Independently of this PR: now that we have the framework for including shaded
>bundles relatively easily, perhaps worth considering making one that applies
>ymnk/jsch-agent-proxy#24 and then switching back to SSHJ?
Absolutely. Let's address that in another PR.
--
You are receiving this
I don't really know the purpose of this change, so let's wait for @iocanel or
close it if there is no update in a reasonable amount of time?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hi @alibazlamit !
The initial comments on this PR haven't been addressed yet; see [Files
Changed](https://github.com/jclouds/jclouds-labs/pull/292/files) tab of this
PR, most notably style-checks. The diff made it looked like that this PR
changed *everything* due to the formatting changes.
> +this.provisioningManager = provisioningManager;
> +}
> +
> +private void SetDataCenterId(String id) {
> +dataCenterId = id;
> +}
> +
> +@Override
> +public NodeAndInitialCredentials
> createNodeWithGroupEncodedIntoName(String group, String name, Template
>
> +final String password = "LTbAHNbcMt";
> +
> +//final org.jclouds.compute.domain.Image image = template.getImage();
> +
> +// provision all volumes based on hardware
> +List volumes = hardware.getVolumes();
> +List volumeIds =
>
> +return api.serverApi().attachVolume(
> +Server.Request.attachVolumeBuilder()
> +.dataCenterId(dataCenterId)
> +.serverId(serverId)
> +
> +}
> +// Last paranoid check
> +waitDcUntilAvailable.apply(dataCenterId);
> +
> +LoginCredentials serverCredentials = LoginCredentials.builder()
> +.user(loginUser)
> +.password(password)
> +.build();
> +
> +destroyVolume(volumeId, dataCenterId);
> +}
> +}
> +// Last paranoid check
> +waitDcUntilAvailable.apply(dataCenterId);
> +
> +LoginCredentials serverCredentials = LoginCredentials.builder()
> +.user(loginUser)
> +
[
https://issues.apache.org/jira/browse/JCLOUDS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469160#comment-15469160
]
Reijhanniel Jearl Campos commented on JCLOUDS-1058:
---
[~nacx] Shouldn't this be closed
> +import org.jclouds.scriptbuilder.statements.java.InstallJDK;
> +import org.jclouds.scriptbuilder.statements.login.AdminAccess;
> +import org.jclouds.ssh.SshClient;
> +import org.jclouds.ssh.SshException;
> +import static org.jclouds.util.Predicates2.retry;
> +import static
> +@Test(groups = "live", singleThreaded = true, testName =
> "ProfitBricksComputeServiceLiveTest")
> +public class ProfitBricksComputeServiceLiveTest extends
> BaseComputeServiceLiveTest {
> +
> +//private static final String TEST_DC_NAME = "computeServiceLiveTest" +
>
> +
> +@Override
> +public DataCenter get() {
> +DataCenter dataCenter = api.create(TEST_DC_NAME, "desc,,,",
> Location.US_LAS.getId());
> +predicate.apply(dataCenter.id());
> +
> +return api.getDataCenter(dataCenter.id());
>
> BTW, regarding the shaded bundle fix, it works, but there is still this error
> when the CLI starts:
>From [this example of
>`startup.properties`](https://github.com/apache/karaf/blob/karaf-2.3.11/assemblies/apache-karaf/src/main/filtered-resources/etc/startup.properties#L75),
> it looks like
[
https://issues.apache.org/jira/browse/JCLOUDS-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469541#comment-15469541
]
ASF subversion and git services commented on JCLOUDS-1074:
--
Commit
> @@ -0,0 +1,79 @@
> +/*
Lots of cleanup and review still to go with these three classes
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Alternative to #78, but addressing the same issue.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-karaf/pull/79
-- Commit Summary --
* Try to use an OSGi-compliant way of loading JSR 223 script engines
-- File Changes --
M
> + return null;
> +}
> + }
> +
> + /**
> + * Iterates through all bundles to get the available @link
> ScriptEngineFactory classes
> + * @return the names of the available ScriptEngineFactory classes
> + * @throws IOException
> + */
> + private List
@nacx Could you give (a CLI built from) this a shot? It looks like it should be
working
```
jclouds> jclouds:compute-service-create --provider aws-ec2 --identity key
--credential secret --name test
Waiting for compute service with name: test.
jclouds> jclouds:location-list --provider aws-ec2
Thanks for the changes, @nacx! Just one more additional thing that I noticed
while working on this: the dependency on
`org.apache.servicemix.bundles.jsch-agentproxy-jsch` in the root POM can
probably be removed too.
--
You are receiving this because you are subscribed to this thread.
Reply to
> +${import.packages}
> +
> +
> +
> +
> +org.apache.maven.plugins
> +maven-shade-plugin
> +2.4.3
> +
> +
> +package
> +
> + shade
> +
> +
> +
Thanks for this, @nacx! I think I'm a little closer to getting the
`OGSiScriptEngineManager` approach that you linked to originally to work - will
try to see if I can figure that out one way or the other soon
--
You are receiving this because you are subscribed to this thread.
Reply to this
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-cli/pull/31
-- Commit Summary --
* Align the startup.properties file with Karaf 2.3.11
* Remove a non-existent feature from the list of features to boot on startup
* Tentatively remove
> @@ -137,13 +137,13 @@
>
> false
>
> -
> +
> @@ -39,11 +39,12 @@
> org/apache/aries/blueprint/org.apache.aries.blueprint.api/${aries.blueprint.api.
>
> org/apache/aries/blueprint/org.apache.aries.blueprint.core/${aries.blueprint.core.version}/org.apache.aries.blueprint.core-${aries.blueprint.core.version}.jar=20
>
>
[
https://issues.apache.org/jira/browse/JCLOUDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan MacDowell updated JCLOUDS-1173:
Description:
I'm seeing different behavior for the BlobStore list method of aws-s3 and
[
https://issues.apache.org/jira/browse/JCLOUDS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan MacDowell updated JCLOUDS-1173:
Attachment: ListTest.java
> List method has different behavior on different cloud
> \ No newline at end of file
> +featuresBoot=jclouds-chef,jclouds-aws-ec2,jclouds-aws-s3
`config:list` and other commands still seem to be present
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Great! Would it make sense to keep this anyway as a sane fallback, or should we
replace it by a runtime exception? Silently returning null is not OK.
We have already the default engine jars in the classpath, and if we throw an
exception users won't be able to workaround it. I'd say that even
Ryan MacDowell created JCLOUDS-1173:
---
Summary: List method has different behavior on different cloud
providers
Key: JCLOUDS-1173
URL: https://issues.apache.org/jira/browse/JCLOUDS-1173
Project:
[
https://issues.apache.org/jira/browse/JCLOUDS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera resolved JCLOUDS-1058.
-
Resolution: Fixed
Fix Version/s: 2.0.0
> ComputeService cannot cancel tasks in
[
https://issues.apache.org/jira/browse/JCLOUDS-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan MacDowell updated JCLOUDS-1146:
Attachment: ReflexiveTest.java
> BlobStoreContext and BlobStore break reflexive propety
62 matches
Mail list logo
