[ https://issues.jboss.org/browse/JGRP-1818?page=com.atlassian.jira.plugin.... ]
Ales Justin updated JGRP-1818:
------------------------------
Summary: Discovery protocol for Google Cloud Storage (was: Discovery protocol for Gogle Cloud Storage)
> Discovery protocol for Google Cloud Storage
> -------------------------------------------
>
> Key: JGRP-1818
> URL: https://issues.jboss.org/browse/JGRP-1818
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1].
> [1] https://developers.google.com/storage/docs/migrating
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Bela Ban created JGRP-1818:
------------------------------
Summary: Discovery protocol for Gogle Cloud Storage
Key: JGRP-1818
URL: https://issues.jboss.org/browse/JGRP-1818
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.5
Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1].
[1] https://developers.google.com/storage/docs/migrating
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
David Lloyd created WFLY-3195:
---------------------------------
Summary: VFS root creation is wrong on Windows
Key: WFLY-3195
URL: https://issues.jboss.org/browse/WFLY-3195
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Reporter: David Lloyd
Assignee: David Lloyd
This may ultimately be a problem with VFS, or with WildFly.
We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/WFLY-3195?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3195:
---------------------------------
Assignee: Tomaz Cerar (was: David Lloyd)
> VFS root creation is wrong on Windows
> -------------------------------------
>
> Key: WFLY-3195
> URL: https://issues.jboss.org/browse/WFLY-3195
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VFS
> Reporter: David Lloyd
> Assignee: Tomaz Cerar
>
> This may ultimately be a problem with VFS, or with WildFly.
> We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira