You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Dave Harvey <dh...@jobcase.com> on 2018/08/03 13:53:14 UTC
S3 discovery and bridge networks
I've been successfully running 2.5 on AWS ECS with host or AWSVPC
networking for the Ignite containers. Is there any way around the fact
that with bridge networking, the Ignite node registers it's unmapped
address on S3?
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
Re: S3 discovery and bridge networks
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
Can you have a virtual network containing all of your nodes, so that their
internal addresses will work?
I have to admit I'm not a devops so I don't know any more specifics.
Regards,
--
Ilya Kasnacheev
2018-08-07 17:07 GMT+03:00 Dave Harvey <dh...@jobcase.com>:
> My understanding: S3 discovery works because the container publishes its
> IP/port in an S3 bucket, and other nodes can read this to determine which
> nodes might be in the cluster. When running in a container using a bridge
> network, the container does not know the external IP address that can be
> used to reach it, so it doesn't have enough information to publish it's IP
> address in S3.
> I'm running in ECS, which starts containers automatically, so I have no
> means to pass in environment variables with additional information.
>
> For this to work, the container would need to be able to determine the
> external identity of its discovery port. I can pass in the external port
> # that we map to, but not the IP address.
>
>
>
> On Mon, Aug 6, 2018 at 10:29 AM, Ilya Kasnacheev <
> ilya.kasnacheev@gmail.com> wrote:
>
>> Hello!
>>
>> Have you tried to specify localAddress for communication and discovery
>> SPIs? If not, can you please elaborate with ifconfig information and stuff?
>>
>> Regards,
>>
>> --
>> Ilya Kasnacheev
>>
>> 2018-08-03 16:53 GMT+03:00 Dave Harvey <dh...@jobcase.com>:
>>
>>> I've been successfully running 2.5 on AWS ECS with host or AWSVPC
>>> networking for the Ignite containers. Is there any way around the fact
>>> that with bridge networking, the Ignite node registers it's unmapped
>>> address on S3?
>>>
>>>
>>> *Disclaimer*
>>>
>>> The information contained in this communication from the sender is
>>> confidential. It is intended solely for use by the recipient and others
>>> authorized to receive it. If you are not the recipient, you are hereby
>>> notified that any disclosure, copying, distribution or taking action in
>>> relation of the contents of this information is strictly prohibited and may
>>> be unlawful.
>>>
>>> This email has been scanned for viruses and malware, and may have been
>>> automatically archived by *Mimecast Ltd*, an innovator in Software as a
>>> Service (SaaS) for business. Providing a *safer* and *more useful*
>>> place for your human generated data. Specializing in; Security, archiving
>>> and compliance. To find out more Click Here
>>> <http://www.mimecast.com/products/>.
>>>
>>
>>
>
>
> *Disclaimer*
>
> The information contained in this communication from the sender is
> confidential. It is intended solely for use by the recipient and others
> authorized to receive it. If you are not the recipient, you are hereby
> notified that any disclosure, copying, distribution or taking action in
> relation of the contents of this information is strictly prohibited and may
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance. To find out more Click Here
> <http://www.mimecast.com/products/>.
>
Re: S3 discovery and bridge networks
Posted by Dave Harvey <dh...@jobcase.com>.
My understanding: S3 discovery works because the container publishes its
IP/port in an S3 bucket, and other nodes can read this to determine which
nodes might be in the cluster. When running in a container using a bridge
network, the container does not know the external IP address that can be
used to reach it, so it doesn't have enough information to publish it's IP
address in S3.
I'm running in ECS, which starts containers automatically, so I have no
means to pass in environment variables with additional information.
For this to work, the container would need to be able to determine the
external identity of its discovery port. I can pass in the external port
# that we map to, but not the IP address.
On Mon, Aug 6, 2018 at 10:29 AM, Ilya Kasnacheev <il...@gmail.com>
wrote:
> Hello!
>
> Have you tried to specify localAddress for communication and discovery
> SPIs? If not, can you please elaborate with ifconfig information and stuff?
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-08-03 16:53 GMT+03:00 Dave Harvey <dh...@jobcase.com>:
>
>> I've been successfully running 2.5 on AWS ECS with host or AWSVPC
>> networking for the Ignite containers. Is there any way around the fact
>> that with bridge networking, the Ignite node registers it's unmapped
>> address on S3?
>>
>>
>> *Disclaimer*
>>
>> The information contained in this communication from the sender is
>> confidential. It is intended solely for use by the recipient and others
>> authorized to receive it. If you are not the recipient, you are hereby
>> notified that any disclosure, copying, distribution or taking action in
>> relation of the contents of this information is strictly prohibited and may
>> be unlawful.
>>
>> This email has been scanned for viruses and malware, and may have been
>> automatically archived by *Mimecast Ltd*, an innovator in Software as a
>> Service (SaaS) for business. Providing a *safer* and *more useful* place
>> for your human generated data. Specializing in; Security, archiving and
>> compliance. To find out more Click Here
>> <http://www.mimecast.com/products/>.
>>
>
>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
Re: S3 discovery and bridge networks
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
Have you tried to specify localAddress for communication and discovery
SPIs? If not, can you please elaborate with ifconfig information and stuff?
Regards,
--
Ilya Kasnacheev
2018-08-03 16:53 GMT+03:00 Dave Harvey <dh...@jobcase.com>:
> I've been successfully running 2.5 on AWS ECS with host or AWSVPC
> networking for the Ignite containers. Is there any way around the fact
> that with bridge networking, the Ignite node registers it's unmapped
> address on S3?
>
>
> *Disclaimer*
>
> The information contained in this communication from the sender is
> confidential. It is intended solely for use by the recipient and others
> authorized to receive it. If you are not the recipient, you are hereby
> notified that any disclosure, copying, distribution or taking action in
> relation of the contents of this information is strictly prohibited and may
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance. To find out more Click Here
> <http://www.mimecast.com/products/>.
>